Re: tagging releases in git

2015-10-10 Thread Barry Warsaw
On Oct 10, 2015, at 04:19 AM, Brian May wrote: >According to the wiki I do this with the following command: > >brian@prune:~/tree/debian/python-modules/django-ajax-selects$ git-dpm tag >git-dpm: ERROR: tag 'upstream/1.3.6' already exists and differs! > >This wasn't the response I was expecting. I

Re: tagging releases in git

2015-10-10 Thread Brian May
On Sun, 11 Oct 2015 at 10:42 Barry Warsaw 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

tagging releases in git

2015-10-09 Thread Brian May
According to the wiki I do this with the following command: brian@prune:~/tree/debian/python-modules/django-ajax-selects$ git-dpm tag git-dpm: ERROR: tag 'upstream/1.3.6' already exists and differs! This wasn't the response I was expecting. I am not sure why it is trying to change the upstream