From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: overseers@sourceware.org
Subject: [Fwd: Welcome to sourceware.org]
Date: Fri, 30 Mar 2007 11:53:00 -0000 [thread overview]
Message-ID: <460CFA09.4070702@linux.vnet.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
Hi ,
I am unable to check out files from systemtap cvs.
Can you please help me resolve this issue.
502 srikar@srikar:~$ echo $CVS_RSH
ssh
503 srikar@srikar:~$ cvs -z9 -d :ext:srikar@sourceware.org:/cvs/systemtap co systemtap
Permission denied (publickey,gssapi-with-mic).
cvs [checkout aborted]: end of file from server (consult above messages if any)
504 srikar@srikar:~$
I had given my ssh rsa key at the time of requesting the account.
--
Thanks and Regards
Srikar
PS: I am forwarding the welcome for your reference.
--
Thanks and Regards
Srikar
[-- Attachment #2: Welcome to sourceware.org --]
[-- Type: message/rfc822, Size: 8109 bytes --]
From: root@sourceware.org
To: srikar@sourceware.org
Cc: ananth@in.ibm.com
Subject: Welcome to sourceware.org
Date: 31 Jan 2007 14:03:00 -0000
Message-ID: <20070131140300.23011.qmail@sourceware.org>
Your account is now active, the login name is srikar@sourceware.org.
Mail sent to that address is forwarded to srikar@linux.vnet.ibm.com.
This forwarding is a convenience so that people who reply directly to CVS
commit mail notes will not get a bounce--publicize it at your own risk.
If your involvement with the project ends at some point, the mail address
will become invalid and I will laugh evilly as people try in vain to
reach you.
You should now have write access to the systemtap repository with
SSH+cvs. Here are lots of details about how to do things.
You don't have general shell access, just CVS remote access. Just about
everything can be done via CVS. If there is some special requirement
that you have where you need shell access, talk to your project's lead
and have them talk to overseers@sourceware.org. In special cases,
we can be flexible on this requirement.
Regarding SSH: If you have provided a Protocol 1 ssh key, you will need
to add the following lines to your a .ssh/config directory:
Host sourceware.org
Protocol 1
This will cause your ssh connections to properly default to protocol 1
when connecting to sourceware.org. If you have provided "Protocol 2"
rsa/dsa keys, then no special action is required.
CVS CVS is used for revision control. If you are not familiar with CVS,
you have some reading to do. http://cvshome.org/ is the central
source for all things CVS. http://cvshome.org/docs/ has some
useful information.
When you want to do a check-in of some change, do it like this:
% cvs update
% cvs diff # carefully verify what you're about to check in!
% cvs commit
All of the sources are under CVS. You have write access to the
files in your repository. Check them out like this:
export CVS_RSH=ssh
cvs -z9 -d :ext:srikar@sourceware.org:/cvs/systemtap co systemtap
After you've checked out some files, you won't need to specify the
CVSROOT (-d) again, it will be picked out of the CVS control files
(the CVS/Root file). You will need to include the -z9; you can put
it in your $HOME/.cvsrc file ("cvs -z9") or add it to your command
line whenever you're doing CVS operations.
If you're going over a modem, you'll definitely want to get this
as compressed as possible.
To avoid the nuisance of having to supply your passphrase for each
operation, you may want to use ssh-agent(1) followed by ssh-add(1)
and entering your passphrase once for all. Either start your
session as a child of ssh-agent or run it as a demon and set the
values of the environment variables SSH_AUTHENTICATION_SOCKET and
SSH_AGENT_PID in each relevant process to what ssh-agent prints
when it starts. To avoid messages about (lack of) X11 forwarding,
put in your $HOME/.ssh/config and entry like:
Host sourceware.org
ForwardX11 no
CVS COMMIT MESSAGES
You can get e-mail notifications for when things are checked in to
your group's repository. There are two notification mailing lists,
one for the web pages for your project and one for the project
source files. To subscribe to your source-file-notification list,
send a message to
systemtap-cvs-subscribe@sourceware.org
To get on a digest of the above list (get one note a day), send a
note to
systemtap-cvs-digest-subscribe@sourceware.org
The body/Subject are ignored in these messages. The From: address
is the one you a requesting to subscribe. To request an arbitrary
address be subscribed, say foo@bar.com, send a note like this:
systemtap-cvs-subscribe-foo=bar.com@sourceware.org
If your project has a web page, then there is a second mailing
list for notifications about changes to them. The addresses are
just like the above ones except they include "-webpages" after the
project name. For instance,
systemtap-webpages-cvs-subscribe@sourceware.org
If this is all a little confusing, just use the all-doing
auto-subscriber at <http://sourceware.org/ml/>.
CVSWEB You can browse changes that are being made to the CVS repository by
going to
http://sourceware.org/cgi-bin/cvsweb.cgi/systemtap?cvsroot=systemtap
HTTP All of the web pages on http://sourceware.org/systemtap/ are
also under CVS. You can create a home page (if one doesn't already
exist) for systemtap by putting files in the htdocs/ directory of
the systemtap CVS module. They will appear instantly (within three
or four seconds, anyway) at http://sourceware.org/systemtap/
If anything is unanswered, please ask your project mailing list.
next reply other threads:[~2007-03-30 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 11:53 Srikar Dronamraju [this message]
2007-03-30 11:59 ` Christopher Faylor
2007-03-30 12:56 ` Frank Ch. Eigler
2007-03-30 14:36 ` Srikar Dronamraju
2007-04-04 12:00 ` Srikar Dronamraju
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=460CFA09.4070702@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.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).