cvs access

cvs access

[Eric Christopher]

For some reason I have to type my ssh key twice when updating sources to
things in the /cvs/src directory.  Anyone else experiencing this?

-eric

cvs access

[Eric Christopher]

For some reason I have to type my ssh key twice when updating sources to
things in the /cvs/src directory.  Anyone else experiencing this?

-eric

Re: cvs access

[Jason Molenda]

On Tue, Oct 31, 2000 at 04:09:16PM -0800, Eric Christopher wrote:
> For some reason I have to type my ssh key twice when updating sources to
> things in the /cvs/src directory.  Anyone else experiencing this?


How many times are you prompted to do

  ssh sourceware echo hi

?  Look over your $CVS_RSH, $CVSROOT and $HOME/.ssh/config for this sort
of thing.  If the ssh echo hi cmd also prompts twice, do ssh -v ... and 
carefully look over all the output.

J

Re: cvs access

[Jason Molenda]

On Tue, Oct 31, 2000 at 04:09:16PM -0800, Eric Christopher wrote:
> For some reason I have to type my ssh key twice when updating sources to
> things in the /cvs/src directory.  Anyone else experiencing this?


How many times are you prompted to do

  ssh sourceware echo hi

?  Look over your $CVS_RSH, $CVSROOT and $HOME/.ssh/config for this sort
of thing.  If the ssh echo hi cmd also prompts twice, do ssh -v ... and 
carefully look over all the output.

J

Re: cvs access

[Tom Tromey]

>> For some reason I have to type my ssh key twice when updating sources to
>> things in the /cvs/src directory.  Anyone else experiencing this?

In some situations cvs likes to contact the server twice.
I don't remember what they are.

I suggest either doing some cvs debugging, or just use ssh-agent and
then never typing your key.

Tom

Re: cvs access

[Tom Tromey]

>> For some reason I have to type my ssh key twice when updating sources to
>> things in the /cvs/src directory.  Anyone else experiencing this?

In some situations cvs likes to contact the server twice.
I don't remember what they are.

I suggest either doing some cvs debugging, or just use ssh-agent and
then never typing your key.

Tom

Re: cvs access

[Eric Christopher]

Jason Molenda wrote:
> 
> On Tue, Oct 31, 2000 at 04:09:16PM -0800, Eric Christopher wrote:
> > For some reason I have to type my ssh key twice when updating sources to
> > things in the /cvs/src directory.  Anyone else experiencing this?
> 
> How many times are you prompted to do
> 
>   ssh sourceware echo hi
> 

Just once.

> ?  Look over your $CVS_RSH, $CVSROOT and $HOME/.ssh/config for this sort
> of thing.  If the ssh echo hi cmd also prompts twice, do ssh -v ... and
> carefully look over all the output.
>

I've been checking out the branch once using the -d option and then
updating without resetting my cvsroot.  Should this matter?

-eric

Re: cvs access

[Eric Christopher]

Jason Molenda wrote:
> 
> On Tue, Oct 31, 2000 at 04:09:16PM -0800, Eric Christopher wrote:
> > For some reason I have to type my ssh key twice when updating sources to
> > things in the /cvs/src directory.  Anyone else experiencing this?
> 
> How many times are you prompted to do
> 
>   ssh sourceware echo hi
> 

Just once.

> ?  Look over your $CVS_RSH, $CVSROOT and $HOME/.ssh/config for this sort
> of thing.  If the ssh echo hi cmd also prompts twice, do ssh -v ... and
> carefully look over all the output.
>

I've been checking out the branch once using the -d option and then
updating without resetting my cvsroot.  Should this matter?

-eric

Re: cvs access

[Jason Molenda]

On Tue, Oct 31, 2000 at 04:25:29PM -0800, Eric Christopher wrote:

> 
> I've been checking out the branch once using the -d option and then
> updating without resetting my cvsroot.  Should this matter?
> 

What about your CVS/Root file, does it have anything suspicious looking?
What does 'cvs -t ...' give you for some command, anything suspicious?
(I think -t didn't work with older cvs's in client/server mode)

Between the env vars I mentioned and these, it should be enough to
spot something suspicious in your environment.  When you get down
to it, cvs just does

   ssh sourceware cvs server

So you need to figure out why it isn't doing that correctly.

J

Re: cvs access

[Jason Molenda]

On Tue, Oct 31, 2000 at 04:25:29PM -0800, Eric Christopher wrote:

> 
> I've been checking out the branch once using the -d option and then
> updating without resetting my cvsroot.  Should this matter?
> 

What about your CVS/Root file, does it have anything suspicious looking?
What does 'cvs -t ...' give you for some command, anything suspicious?
(I think -t didn't work with older cvs's in client/server mode)

Between the env vars I mentioned and these, it should be enough to
spot something suspicious in your environment.  When you get down
to it, cvs just does

   ssh sourceware cvs server

So you need to figure out why it isn't doing that correctly.

J

Re: cvs access

[Eric Christopher]

Jason Molenda wrote:
> 
> On Tue, Oct 31, 2000 at 04:25:29PM -0800, Eric Christopher wrote:
> 
> >
> > I've been checking out the branch once using the -d option and then
> > updating without resetting my cvsroot.  Should this matter?
> >
> 
> What about your CVS/Root file, does it have anything suspicious looking?
> What does 'cvs -t ...' give you for some command, anything suspicious?
> (I think -t didn't work with older cvs's in client/server mode)

Figgered it out.  I have two different entries in the Root files across
the checkout.  Some say gcc.gnu.org and other say sources.redhat.com :)

-eric

Re: cvs access

[Eric Christopher]

Jason Molenda wrote:
> 
> On Tue, Oct 31, 2000 at 04:25:29PM -0800, Eric Christopher wrote:
> 
> >
> > I've been checking out the branch once using the -d option and then
> > updating without resetting my cvsroot.  Should this matter?
> >
> 
> What about your CVS/Root file, does it have anything suspicious looking?
> What does 'cvs -t ...' give you for some command, anything suspicious?
> (I think -t didn't work with older cvs's in client/server mode)

Figgered it out.  I have two different entries in the Root files across
the checkout.  Some say gcc.gnu.org and other say sources.redhat.com :)

-eric

cvs access

[Brendan Kehoe]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!  Benjamin suggested that I write you guys to get set up for CVS write 
access to be able to do checkins to libstdc++.

This is my public key:

1024 35 
129827975462833498779151962939119814906156657100268071283919317007825047249595446033730097413535550951884673757206861056562634091995353413034048046683473706863868702567025303243102195809587477410206527346428573771324847808542920609562562981990444460185083054922691878985621573019026310649301741743315520625179 
brendan@zen.org

Thanks!
B

- -- 
Brendan Kehoe                                               brendan@zen.org

http://www.zen.org/~brendan/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+045sReWQaPkbt58RAgaOAJoDfFuqITB8a4O1qpViru6b1vhL6ACgtC6h
q2YQe0V+V62uOzQZ8mdfyV0=
=/osK
-----END PGP SIGNATURE-----

Re: cvs access

[Christopher Faylor]

On Tue, May 27, 2003 at 12:12:15PM -0400, Brendan Kehoe wrote:
>Hi!  Benjamin suggested that I write you guys to get set up for CVS write 
>access to be able to do checkins to libstdc++.
>
>This is my public key:

You already had this key on sourceware but you needed to be in the libstdc++
group.  I've added you.

cgf

Re: cvs access

[Benjamin Kosnik]

>You already had this key on sourceware but you needed to be in the libstdc++
>group.  I've added you.

Thanks!

-benjamin