On Sun, 11 Oct 2015 at 10:42 Barry Warsaw <ba...@debian.org> wrote: > What I've done, and it's probably horrible, is to just `git-dpm tag > --refresh` > and then `git push --tags --force`. >
That does look yuck. If my vague understanding is correct, it seems that git-dpm wants to assign the tags to the same commits, but references it differently. ie. it references the parent commit instead of the actual commit. I updated the tag names to *-new/*, created tags, and compared the tags using gitk: Tag: upstream-new/1.3.6 tree ee9a409e99194f61677a7f1db264ad195e34e674 parent 6301bde3e906597778cf9633d3bb15934351de55 author SVN-Git Migration <python-modules-t...@lists.alioth.debian.org> 1444319334 -0700 committer SVN-Git Migration <python-modules-t...@lists.alioth.debian.org> 1444319334 -0700 Imported Upstream version 1.3.6 Tag: upstream/1.3.6 object 93a165c58b76bbb3702ea7d8d96c190b8d056ae2 type commit tag upstream/1.3.6 tagger SVN-Git Migration <python-modules-t...@lists.alioth.debian.org> 1444319335 -0700 Upstream version 1.3.6 (the message is different too, not sure that is an issue) Where 93a165c58b76bbb3702ea7d8d96c190b8d056ae2 is the actual commit and 6301bde3e906597778cf9633d3bb15934351de55 was the parent commit. I would guess this difference is why it wants to update the tags.
