Trying to add a tag to an new release of a DPMT migrated package I get
the following error:

brian@prune:~/tree/debian/python-modules/django-ajax-selects$ git-dpm
tag
git-dpm: ERROR: tag 'upstream/1.3.6' already exists and differs!

To me this doesn't make a lot of sense. The tag already exists, and it
is pointing at the correct revision, why does git-dpm have to change it?

The repository is available from git.debian.org:

brian@prune:~/tree/debian/python-modules/django-ajax-selects$ git remote -v
origin git+ssh://git.debian.org/git/python-modules/packages/django-ajax-selects.git (fetch)
origin git+ssh://git.debian.org/git/python-modules/packages/django-ajax-selects.git (push)

(Also on a related note, since it is possible this is due to different
tag formats or something, shouldn't it be possible to create signed
tags?  If it is possible, doesn't seem obvious how. Maybe signed should
be the default even?)

Hi,

I have the same error when trying to tag a minor version on pylint-plugin-utils.
The only differences between the previous tag are the debian/control
file and the debian/changelog. Nothing related to upstream.

Should I do a "git-dpm tag --refresh" to fix that?
Is it just because it's signed with another key during the git
migration? (Not sure if it's really signed or if it is trying to sign
it now)

Package in alioth:
https://anonscm.debian.org/cgit/python-modules/packages/pylint-plugin-utils.git/

Thanks for your help,
Joseph