There's a hook on the Cygwin Git infrastructure that is refusing to
accept updated tags for the git package. There's no explanation of why
the push is being rejected, but this worked four weeks ago when I pushed
v2.37.3-1, and is failing now.
I initially encountered the failure on the GitHub runners, but I see the
same behaviour when I attempt to reproduce the behaviour locally:
$ git show v2.38.0-1
tag v2.38.0-1
Tagger: me-and <[email protected]>
Date: Mon Oct 3 22:40:46 2022 +0000
v2.38.0-1
commit 97e2629305827082566bd7d56fc9a0544b4603e7 (tag: v2.38.0-1,
origin/next, origin/main, origin/HEAD)
Merge: f3e0456 65b7884
Author: Adam Dinwoodie <[email protected]>
Date: Mon Oct 3 19:18:59 2022 +0100
Merge branch 'v2.38.0'
$ git remote -v
cygwin https://cygwin.com/git/cygwin-packages/git.git (fetch)
cygwin [email protected]:git/cygwin-packages/git.git (push)
origin https://github.com/me-and/Cygwin-Git (fetch)
origin https://github.com/me-and/Cygwin-Git (push)
$ git push cygwin v2.38.0-1
Enumerating objects: 10, done.
Counting objects: 100% (10/10), done.
Delta compression using up to 4 threads
Compressing objects: 100% (8/8), done.
Writing objects: 100% (8/8), 762 bytes | 381.00 KiB/s, done.
Total 8 (delta 6), reused 0 (delta 0), pack-reused 0
remote: FATAL: W refs/tags/v2.38.0-1 git/cygwin-packages/git Adam_Dinwoodie
DENIED by fallthru
remote: error: hook declined to update refs/tags/v2.38.0-1
To cygwin.com:git/cygwin-packages/git.git
! [remote rejected] v2.38.0-1 -> v2.38.0-1 (hook declined)
error: failed to push some refs to 'cygwin.com:git/cygwin-packages/git.git'
Is this a bug in the server side hooks, or have I missed some expected
change in behaviour here? It's not a big deal -- I'm not using the
Cygwin Git infrastructure for anything other than discoverability, and
my working repositories are the ones on GitHub -- but if nothing else
I'd like to know if I've inadvertently broken something!
Adam
