From: "Martin Liška" <mliska@suse.cz>
To: Mark Wielaard <mark@klomp.org>
Cc: elfutils-devel@sourceware.org, buildbot@sourceware.org
Subject: Re: buildbot users try branch builders for elfutils
Date: Mon, 15 Aug 2022 12:08:23 +0200 [thread overview]
Message-ID: <9d67b906-357b-d42e-76dc-4b582018e645@suse.cz> (raw)
In-Reply-To: <YvoZi3VniP24hQNa@wildebeest.org>
On 8/15/22 12:01, Mark Wielaard wrote:
> Hi Martin,
>
> On Mon, Aug 15, 2022 at 09:55:13AM +0200, Martin Liška wrote:
>> On 7/28/22 17:26, Mark Wielaard wrote:
>>> I setup git users try branches for elfutils. If you have commit
>>> access to elfutils.git you can now [...]
>>
>> I would like to try this great feature!
>> [...]
>> But I get:
>>
>> git push origin PR29474-fix-debuginfod-concurrency:users/marxin/try-PR29474-fix-debuginfod-concurrency
>> [...]
>> error: remote unpack failed: unable to create temporary object directory
>> To ssh://sourceware.org/git/elfutils.git
>> ! [remote rejected] PR29474-fix-debuginfod-concurrency -> users/marxin/try-PR29474-fix-debuginfod-concurrency (unpacker error)
>> error: failed to push some refs to 'ssh://sourceware.org/git/elfutils.git'
>>
>> Can you please take a look what happens?
>
> That unhelpful error message tries to say you are not an elfutils
> developer.
>
> Lets fix that. I added you to the elfutils groups. Please remember,
> with great power comes great responsibility (aka, please reread the
> elfutils CONTRIBUTING file).
>
> You should now also be able to use the users try branches. So please
> try again.
Thanks Mark, it works nice!
Martin
>
> Cheers,
>
> Mark
prev parent reply other threads:[~2022-08-15 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 15:26 Mark Wielaard
2022-08-15 7:55 ` Martin Liška
2022-08-15 10:01 ` Mark Wielaard
2022-08-15 10:08 ` Martin Liška [this message]
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=9d67b906-357b-d42e-76dc-4b582018e645@suse.cz \
--to=mliska@suse.cz \
--cc=buildbot@sourceware.org \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.org \
/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).