public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@igalia.com>
To: overseers@sourceware.org
Subject: Re: Request from Andy Wingo
Date: Wed, 11 Mar 2015 10:48:00 -0000	[thread overview]
Message-ID: <877funn725.fsf@igalia.com> (raw)
In-Reply-To: <20150309184014.GA5274@ednor.casa.cgf.cx> (Christopher Faylor's message of "Mon, 9 Mar 2015 14:40:14 -0400")

[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]

On Mon 09 Mar 2015 19:40, Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org> writes:

> On Mon, Mar 09, 2015 at 07:27:40PM +0100, Andy Wingo wrote:
>>On Mon 09 Mar 2015 16:07, Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org> writes:
>>
>>> On Mon, Mar 09, 2015 at 07:35:21AM -0000, wingo@igalia.com wrote:
>>>>Andy Wingo would like to be added to sourceware.org.
>>>>
>>>>For more information, check out:
>>>>http://sourceware.org/cgi-bin/pdw/queue.cgi
>>>>
>>>>Or, check the specific request here:
>>>>http://sourceware.org/cgi-bin/pdw/details.cgi?file=4222787.59222
>>>
>>>Sorry but no.
>>>
>>>Assuming that xdje42@gmail.com is Doug Evans, he's a
>>>write-after-approval submitter and cannot approve gcc access.
>>
>>The request is for GDB, not GCC, and indeed it's Doug Evans.  Perhaps I
>>mis-entered the details?
>
> Sorry.  My mistake.  It was for gdb.

I received the sourceware.org account creation mail but it seems
something went wrong with the SSH key setup:

  $ ssh -vv sourceware.org
  [...]
  debug1: Offering RSA public key: /home/wingo/.ssh/id_rsa
  debug2: we sent a publickey packet, wait for reply
  debug1: Authentications that can continue: publickey
  debug1: Offering RSA public key: wingo@rusty
  debug2: we sent a publickey packet, wait for reply
  debug1: Authentications that can continue: publickey
  debug2: we did not send a packet, disable method
  debug1: No more authentication methods to try.
  Permission denied (publickey).

My local username is "wingo", which AFAIK is the same as the
sourceware.org name, so that shouldn't be the issue.  Could it be that I
mangled the SSH pubkey?  I am attaching my public key again.

Andy


[-- Attachment #2: authorized_keys --]
[-- Type: application/octet-stream, Size: 738 bytes --]

ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAgEAniIBKe3+toYN/4MtEnN8osjwkrlYlXfdRU1vXtjE1MRbPyiQ2D1MVFx6VWRz7VAKXToUeRqAqSm5jS+34r5erKbNGJnRcyOjryyDGCvwAHcVeAg0dbR75uwesw+0Bymhqw8CSCjauySWusMmB1is6Bow7G+tv9I91Pkky1WrgYu/JQDRpN00GCGbhrS2h2JaqIlgXRuzj9/ls8iJnPDNMi1qGoQBWXOhPFxURZMBPdUgFQeayQ96NvZdSHDlKCEgv9Nu1zvfpKsR34gwuC/V3/+DRvsRERXb3gLRQaZAPEAkAn/Qwu/SAMe7shgdKRiQqnpNsDGRWHCVX3E7QpSjqqmfbWaoKG1MITmm+4B/b+OWNThANCNxmkw+YSgqPnXcwfot5pBNGL/2MwdYLr9shidRrd2s2Sy+vLdaBlaaKSMuCIWt3JtVmj+yxXjJmHrnaj+oiNLTI/++La52smRgU9mk+0888Uz852p9WjeQ9C3dd07sdx96pGWDSkmUmoOaLxyn1ypIm5PvOoSZXs9/82sE5JUPmlVgPr9mF2vDYmydAo56uk9qUXD/4pdddzlWfmldsIoo4cAYFG+4tTcwOG/6TDeSWv0sS+9Gw1BBGvYLMpXBBn8TtRRt+jEDyvV2u7U5VK/h/wcPIVyiVXQkdOrkAOC3THVb8CUo+yWevHU= wingo@harpy.local

  reply	other threads:[~2015-03-11 10:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09  7:35 wingo
2015-03-09 15:08 ` Christopher Faylor
2015-03-09 18:27   ` Andy Wingo
2015-03-09 18:40     ` Christopher Faylor
2015-03-11 10:48       ` Andy Wingo [this message]
2015-03-11 12:26         ` Andy Wingo
2015-03-11 12:32           ` Ian Lance Taylor
2015-03-11 12:44             ` Andy Wingo
2015-03-11 12:30         ` Ian Lance Taylor

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=877funn725.fsf@igalia.com \
    --to=wingo@igalia.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).