public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Adam Dinwoodie <adam@dinwoodie.org>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Cygwin Git repos refusing push
Date: Tue, 4 Oct 2022 13:28:27 +0100	[thread overview]
Message-ID: <a44d492a-be79-fdbd-3cd5-cc4ac703e59e@dronecode.org.uk> (raw)
In-Reply-To: <20221004075508.akit65zoarxid6r2@lucy.dinwoodie.org>

On 04/10/2022 08:55, Adam Dinwoodie wrote:
> 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.
[...]
>      
>      $ 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

Thanks for reporting this.

A few weeks ago, I made a change to prevent pushes to branches which 
don't have a defined role in our scheme (i.e anything not 'master' or 
'playground'), and accidentally prevented tags from being pushed as well.

I've adjusted the gitolite configuration so this should work again.

In passing, I notice that this repo doesn't have a master branch, only 
tags, as that has never been pushed to, which may or may not be what you 
intended.


  reply	other threads:[~2022-10-04 12:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04  7:55 Adam Dinwoodie
2022-10-04 12:28 ` Jon Turney [this message]
2022-10-04 14:02   ` Adam Dinwoodie
2022-10-08 13:12     ` Jon Turney
2022-10-08 13:23       ` Adam Dinwoodie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a44d492a-be79-fdbd-3cd5-cc4ac703e59e@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=adam@dinwoodie.org \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).