[Bug 684247] New: git won't let me fix a bad tag

["sysadmin" (bugzilla.gnome.org) <bugzilla gnome org>]

https://bugzilla.gnome.org/show_bug.cgi?id=684247
  sysadmin | Git | unspecified

           Summary: git won't let me fix a bad tag
    Classification: Infrastructure
           Product: sysadmin
           Version: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: Git
        AssignedTo: sysadmin-maint gnome bugs
        ReportedBy: danw gnome org
         QAContact: sysadmin-maint gnome bugs
     GNOME version: ---


I did "git push --tags origin master" and got back:

 * [new tag]         2.33.14 -> 2.33.14
 ! [rejected]        master -> master (non-fast-forward)
error: failed to push some refs to
'ssh://danw git gnome org/git/glib-networking'
hint: Updates were rejected because the tip of your current branch is behind
etc etc etc

(because a translator snuck in a commit while I wasn't paying attention). So I
pulled, rebased, re-tagged, and tried to push again, but was told that it's not
allowed to change a tag that's already been pushed. So now I'm in a situation
where I can either (a) make the release from the existing tag which is not on
any branch, or (b) have the tag point to the wrong place and use a different
tag to identify the actual release.

I did (b), but that's lame.

So this is a request both for someone to fix the tags (delete the existing
2.33.14 and rename 2.33.14.1 to 2.33.14), and maybe to rethink the policy. (Do
we have any information about how often the different commit-refusals get hit?
If no one is hitting this accidentally, then I don't think there's any reason
to block people from doing it on purpose.)

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the QA contact of the bug.
You are watching the assignee of the bug.