public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jason Eckhardt <jle@owlnet.rice.edu>
To: Christopher Faylor <cgf@redhat.com>
Cc: <overseers@gcc.gnu.org>
Subject: Re: Update SSH key request
Date: Thu, 07 Aug 2003 22:53:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.33.0308071749010.21804-100000@ural.owlnet.rice.edu> (raw)
In-Reply-To: <20030807210232.GB6438@redhat.com>



On Thu, 7 Aug 2003, Christopher Faylor wrote:

> On Thu, Aug 07, 2003 at 03:43:24PM -0500, Jason Eckhardt wrote:
> >I currently have write access to the gcc repository, but I would
> >like to update my SSH key.  I'd prefer to use the same key that
> >is already active for my sources.redhat.com account.
>
> gcc.gnu.org is the same system as sources.redhat.com.  If you are using
> a key for sources.redhat.com, it will work for gcc.gnu.org, assuming that
> you have write permissions to the repository.A

  I haven't used the gcc repository for 2 years or so, and today
  it doesn't work (using same password as sources).:
jle% cvs co gcc
Enter passphrase for RSA key 'jle@sathanas':
cvs server: Updating gcc
cvs server: failed to create lock directory for `/cvs/gcc/gcc' (/cvs/gcc/gcc/#cvs.lock): Permission denied
i
  Could my write permission have been inadvertently (or not) removed?
  Do you know whom I should contact?

  Thanks, Jason.


  reply	other threads:[~2003-08-07 22:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-07 20:43 Jason Eckhardt
2003-08-07 21:02 ` Christopher Faylor
2003-08-07 22:53   ` Jason Eckhardt [this message]
2003-08-22  5:08     ` law
2003-08-22 15:12       ` Jason Eckhardt
2003-08-22 15:32       ` Christopher Faylor
2003-08-22  4:59 ` law

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=Pine.GSO.4.33.0308071749010.21804-100000@ural.owlnet.rice.edu \
    --to=jle@owlnet.rice.edu \
    --cc=cgf@redhat.com \
    --cc=overseers@gcc.gnu.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).