From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITA] nghttp2, mingw64-{x86_64,i686}-nghttp2
Date: Sat, 29 May 2021 11:09:06 +0100 [thread overview]
Message-ID: <c1aa73f3-51aa-4fd2-b9f1-d1fecb19c3c8@dronecode.org.uk> (raw)
In-Reply-To: <1fe9bb8f-327d-c9fc-9b5c-31c7471073d1@gmail.com>
On 29/05/2021 07:12, Marco Atzeri via Cygwin-apps wrote:
> On 29.05.2021 06:37, Brian Inglis wrote:
[...]
>>
>> until I can get git-cygwin-packages working again - see below!
>>
>>>> Changed maintainership to you (only for them this time)
>>>
>>> Thank you very much - appreciate that!
>>> Repology.org dropped the extraneous maintainership adds/removes ;^>
>>
>> Do I also have ownership of:
>
> should be
> but Jon is the expert here
>
>> I am getting the following responses whenever I try to push to either
>> playground
>> or master branches!
[...]
>>
>> $ git push
>> Enumerating objects: 11, done.
>> Counting objects: 100% (11/11), done.
>> Delta compression using up to 4 threads
>> Compressing objects: 100% (7/7), done.
>> Writing objects: 100% (9/9), 2.23 KiB | 326.00 KiB/s, done.
>> Total 9 (delta 2), reused 0 (delta 0), pack-reused 0
>> remote: 'there can be only one!' at
>> /sourceware1/cygwin-staging/gitolite.git/src/VREF/HIGHLANDER line 27.
>> remote: FATAL: VREF/HIGHLANDER/cygport: helper program exit status 65280
>> remote: error: hook declined to update refs/heads/playground
>> To ssh://cygwin/git/cygwin-packages/nghttp2
>> ! [remote rejected] playground -> playground (hook declined)
>> error: failed to push some refs to
>> 'ssh://cygwin/git/cygwin-packages/nghttp2'
This is a new trigger I turned on recently, which (is supposed to)
prevent pushes of trees which contain more than one .cygport file
(since that complicates navigating from source pacakage name to git
history of the .cygport file in ways I have no interest in implementing)
I've tuned this down to a warning at the moment (and made it a bit
clearer) so you should be able to proceed.
Can you provide a commit id which triggers this which but shouldn't, and
I'll try to work out why...
next prev parent reply other threads:[~2021-05-29 10:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 17:06 Brian Inglis
2021-05-28 18:33 ` Marco Atzeri
2021-05-28 23:18 ` Brian Inglis
2021-05-29 4:37 ` Brian Inglis
2021-05-29 6:12 ` Marco Atzeri
2021-05-29 10:09 ` Jon Turney [this message]
2021-05-29 10:42 ` Achim Gratz
2021-05-29 11:18 ` Achim Gratz
2021-05-29 16:55 ` Brian Inglis
2021-05-29 18:01 ` Achim Gratz
2021-05-29 18:34 ` Brian Inglis
2021-05-29 16:18 ` Brian Inglis
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=c1aa73f3-51aa-4fd2-b9f1-d1fecb19c3c8@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).