CurseForge

692 - Pushing a git tag causes Alpha rebuild

What steps will reproduce the problem?
On a local and uptodate checkout of the git repo
1. git tag tagname
2. git push --tags
3. Profit

What is the expected output? What do you see instead?

Expected output is the packager produces a Beta or Release package based on the tag pushed.

Actual output is the packager produces a Beta or Release package based on the tag pushed, and a repeat of the Alpha package for the HEAD commit with the same name and change log but a different MD5 sum.

At what time and date (year, month, day) did you get this bug? (Include your timezone)

7:40pm 4th October 2008 AEST (+10UTC)

User When Change
Torhal Mon, 22 Aug 2011 17:22:08 Changed status from New to Fixed
Torhal Fri, 03 Jun 2011 17:02:34 Changed assigned to from None to prencher
Ackis Tue, 01 Feb 2011 18:00:52 Changed assigned to from ckknight to None
Ackis Fri, 27 Mar 2009 19:50:05 Changed component from None to Component #18
Ackis Mon, 19 Jan 2009 18:43:54 Changed assigned to from None to ckknight
TBBle Sat, 04 Oct 2008 09:44:12 Create

You must login to post a comment. Don't have an account? Register to get one!

  • 2 comments
  • Avatar of anmoch anmoch Sat, 04 Oct 2008 11:37:03

    Ok so I apparently spoke too soon. It'll be worth investigating why the re-packaged alpha gets a different MD5, though my money is on a timestamp field somewhere in the file. Not that it really hurts much, does it?

    Still, don't push unannotated tags.

  • Avatar of anmoch anmoch Sat, 04 Oct 2008 11:33:30

    Don't use 'git tag', it makes unannotated tags (use -a or -s).
    If you use 'git tag', don't push them.
    If you push them, don't be surprised.

  • 2 comments

Facts

Last updated on
22 Aug 2011
Reported on
04 Oct 2008
Status
Fixed - Developer made requested changes. QA should verify.
Type
Defect - A shortcoming, fault, or imperfection
Priority
Medium - Normal priority.

Reported by

Possible assignees

Votes (Total: +1, Average: +1.0)