Hi Tobias, On Sun, Nov 20, 2016 at 02:06:08PM +0100, Dr. Tobias Quathamer wrote: > there's already an annotated tag with the same name (debian/1.1.0-2) in the > git repository.
Unfortunately not, the tag is neither signed nor annotated: # git show debian/1.1.0-2 commit 7c465867c85c4ed3c70ebe912355fbf8d3ce5971 Author: Dr. Tobias Quathamer <to...@debian.org> Date: Tue Nov 15 14:26:53 2016 +0100 Prepare release (You can tell since it points directly to a commit object.) > If I sign the tag, I would need to delete the remote tag and push it again. > This would mess with everybody's git clone'd local repository. I'm not sure > that would be wise. It should be fine if you correct the tag as long as it has been announced. I recently had half a dozen backports where I had to force-push new tags because my sponsor modified the changelog after the request ;-). > I suggest that you put the above mentioned ~/gbp.conf stanza into > debian/gbp.conf, the file already exists. This way, the next uploader would > sign the tag, even if they don't have this option in their home directory. Good suggestion. Should we make this a default for all golang- packages? Regards, Peter _______________________________________________ Pkg-go-maintainers mailing list Pkgfirstname.lastname@example.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers