From: Andrew Cagney <ac131313@redhat.com>
To: overseers@sources.redhat.com
Subject: [Fwd: Can I get read access to /cvs/gdbadmin?]
Date: Wed, 26 Feb 2003 22:44:00 -0000 [thread overview]
Message-ID: <3E5D43F2.8010209@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 81 bytes --]
Is it possible to enable pserver access to the /cvs/gdbadmin repository?
Andrew
[-- Attachment #2: Can I get read access to /cvs/gdbadmin? --]
[-- Type: message/rfc822, Size: 2435 bytes --]
From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com, gdb@sources.redhat.com
Subject: Can I get read access to /cvs/gdbadmin?
Date: Wed, 26 Feb 2003 16:12:21 -0600
Message-ID: <200302262212.h1QMCLq32095@duracef.shout.net>
I'm looking at pr gdb/708, which says that the snapshot tarballs
do not build. The problem is still happening, with both the
branch and HEAD tarballs.
I'm trying to cvs checkout the gdbadmin scripts so I can debug the
snapshot script, per the instructions near the bottom of:
http://sources.redhat.com/gdb/current/
Namely:
# this works fine
$ cvs -z9 -d :pserver:anoncvs@sources.redhat.com:/cvs/gdbadmin login
# this fails ...
$ cvs -z9 -d :pserver:anoncvs@sources.redhat.com:/cvs/gdbadmin co .
cvs server: Updating .
cvs server: failed to create lock directory for `/cvs/gdbadmin' (/cvs/gdbadmin/#cvs.lock): Permission denied
cvs server: failed to obtain dir lock in repository `/cvs/gdbadmin'
cvs [server aborted]: read lock failed - giving up
I get the same problem with -d :ext:MYNAME@sources.redhat.com:/cvs/gdbadmin.
Is this some kind of permission problem on the sware side?
Or do I need to apply for separate permission to read gdbadmin?
Help please,
Michael C
next reply other threads:[~2003-02-26 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 22:44 Andrew Cagney [this message]
2003-02-27 15:49 ` law
2003-02-27 19:40 ` Andrew Cagney
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=3E5D43F2.8010209@redhat.com \
--to=ac131313@redhat.com \
--cc=overseers@sources.redhat.com \
/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).