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 |
|---|---|---|
| Ackis | Fri, 27 Mar 2009 19:50:05 | Changed component from None to Repositories |
| Ackis | Mon, 19 Jan 2009 18:43:54 | Changed assigned to from None to ckknight |
| TBBle | Sat, 04 Oct 2008 09:44:12 | Create |
- 2 comments
- 2 comments
Facts
- Last updated on
- 27 Mar 2009
- Reported on
- 04 Oct 2008
- Status
- New - Issue has not had initial review yet.
- Type
- Defect - A shortcoming, fault, or imperfection
- Priority
- Medium - Normal priority.
- Component
- Repositories
- #2
anmoch Sat, 04 Oct 2008 11:37:03Ok 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.
- #1
anmoch Sat, 04 Oct 2008 11:33:30Don'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.