From: "CHIGOT, CLEMENT" <clement.chigot@atos.net>
To: "overseers@sourceware.org" <overseers@sourceware.org>
Cc: David Edelsohn <dje.gcc@gmail.com>
Subject: Write access for GCC not working
Date: Tue, 19 Oct 2021 11:47:34 +0000 [thread overview]
Message-ID: <PA4PR02MB66865BCC9BBA07E1D0FF671EEABD9@PA4PR02MB6686.eurprd02.prod.outlook.com> (raw)
Hi,
A few months ago, I requested a write access for both GCC and binutils.
I did push some patches to binutils. But I didn't have the needs for GCC until today.
Thus I try to setup it thanks to "https://gcc.gnu.org/gitwrite.html". But it seems that I don't have the write access.
$ git push
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 4 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 413 bytes | 413.00 KiB/s, done.
Total 3 (delta 2), reused 0 (delta 0)
error: remote unpack failed: unable to create temporary object directory
To git+ssh://gcc.gnu.org/git/gcc.git
! [remote rejected] master -> master (unpacker error)
error: failed to push some refs to 'git+ssh://helflym@gcc.gnu.org/git/gcc.git'
Is it because I didn't push anything yet and thus it has been disabled or is there something else wrong ?
Note I don't have anything to push to binutils so I can't test if I have the same problem too. However,
my ssh to gcc.gnu.org doesn't seem to reject me.
Thanks in advance,
Clément Chigot
ATOS Bull SAS
1 rue de Provence - 38432 Échirolles - France
next reply other threads:[~2021-10-19 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 11:47 CHIGOT, CLEMENT [this message]
2021-10-19 12:27 ` Mark Wielaard
2021-10-19 12:28 ` David Edelsohn
2021-10-19 12:32 ` Mark Wielaard
2021-10-19 12:34 ` CHIGOT, CLEMENT
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=PA4PR02MB66865BCC9BBA07E1D0FF671EEABD9@PA4PR02MB6686.eurprd02.prod.outlook.com \
--to=clement.chigot@atos.net \
--cc=dje.gcc@gmail.com \
--cc=overseers@sourceware.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).