From: Nick Clifton <nickc@redhat.com>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Christian Groessler <chris@groessler.org>
Subject: Fwd: Re: lost access to binutils source repository
Date: Tue, 21 Jul 2020 11:13:37 +0100 [thread overview]
Message-ID: <e7d7cdb9-b685-50e0-71dd-422a74dc82d5@redhat.com> (raw)
In-Reply-To: <1b274ed7-520e-0366-f15b-abe68c777fd2@groessler.org>
Hi Guys,
Can you help Christian ? He appears to have lost write access
to the sourceware repository:
Cheers
Nick
-------- Forwarded Message --------
Subject: Re: lost access to binutils source repository
Date: Mon, 20 Jul 2020 20:15:52 +0200
From: Christian Groessler <chris@groessler.org>
To: Nicholas Clifton <nickc@redhat.com>
Hello Nick,
sorry to nag you directly, IDK where else to ask.
> it seems that I've lost (write) access to the binutils repo. I don't
> remember when it worked last time, probably some months ago.
>
> [es45:~/tmp/binutils-gdb]$ git remote -v
> sourceware ssh://sourceware.org/git/binutils-gdb.git (fetch)
> sourceware ssh://sourceware.org/git/binutils-gdb.git (push)
> [es45:~/tmp/binutils-gdb]$ git fetch sourceware
> cpg@sourceware.org: Permission denied (publickey).
> fatal: Could not read from remote repository.
> I am using a pub/priv key to access the repo. Has something changed?
I don't know when it started. My binutils involvement was dormant the
recent months/years.
I'm "cpg" on sourceware.org. My pub/priv key to access sourceware is
DSA. Maybe that's not allowed anymore.
Could you give me a hand?
--------------------------------------------------------------------
next parent reply other threads:[~2020-07-21 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1b274ed7-520e-0366-f15b-abe68c777fd2@groessler.org>
2020-07-21 10:13 ` Nick Clifton [this message]
2020-07-21 10:41 ` Frank Ch. Eigler
2020-07-21 11:27 ` Christian Groessler
2020-07-21 11:29 ` Frank Ch. Eigler
2020-07-21 11:44 ` Christian Groessler
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=e7d7cdb9-b685-50e0-71dd-422a74dc82d5@redhat.com \
--to=nickc@redhat.com \
--cc=chris@groessler.org \
--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).