From: law@redhat.com
To: Jason Eckhardt <jle@owlnet.rice.edu>
Cc: Christopher Faylor <cgf@redhat.com>, overseers@gcc.gnu.org
Subject: Re: Update SSH key request
Date: Fri, 22 Aug 2003 05:08:00 -0000 [thread overview]
Message-ID: <200308220508.h7M586Qq001410@speedy.slc.redhat.com> (raw)
In-Reply-To: Your message of "Thu, 07 Aug 2003 17:53:27 CDT." <Pine.GSO.4.33.0308071749010.21804-100000@ural.owlnet.rice.edu>
In message <Pine.GSO.4.33.0308071749010.21804-100000@ural.owlnet.rice.edu>, Jas
on Eckhardt writes:
> 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?
I don't see how it could be failing. Did someone perhaps already fix
this?
[root@sourceware gcc]# groups jle
jle : binutils gcc src
[root@sourceware gcc]# ls -la /cvs/gcc/gcc | more
total 11224
drwxrwsr-x 30 anoncvs gcc 4096 Aug 22 05:04 .
drwxrwsr-x 9 anoncvs gcc 4096 Aug 21 22:06 ..
-r--rw-r-- 1 gccadmin gcc 23015 Aug 18 16:41 .cvsignore,v
-r--r--r-- 1 dnovillo gcc 42464 Aug 18 06:04 ABOUT-NLS,v
drwxrwsr-x 3 law gcc 4096 Aug 13 21:18 Attic
-r--rw-r-- 1 gccadmin gcc 38612 Aug 18 16:41 COPYING,v
[ ... ]
ie, you're in the "gcc" group, which should be all you need to be able to
do things to the GCC repository.
jeff
next prev parent reply other threads:[~2003-08-22 5:08 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
2003-08-22 5:08 ` law [this message]
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=200308220508.h7M586Qq001410@speedy.slc.redhat.com \
--to=law@redhat.com \
--cc=cgf@redhat.com \
--cc=jle@owlnet.rice.edu \
--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).