Re: Problems with cygwin cvs over ssh.

On Mar 24 04:03, Charles Wilson wrote: > Eric Blake wrote: > >My experience with cvs-1.11.21-1 is that it loses track of conflicts. In > >other words, in cvs-1.11.17, if I do: > > > >$ cvs up > >C foo > >$ cvs up > >C foo > > > >but in cvs-1.11.21, I get: > >$ cvs up > >C foo > >$ cvs up > >M foo

Re: Problems with cygwin cvs over ssh.

Eric Blake wrote: My experience with cvs-1.11.21-1 is that it loses track of conflicts. In other words, in cvs-1.11.17, if I do: $ cvs up C foo $ cvs up C foo but in cvs-1.11.21, I get: $ cvs up C foo $ cvs up M foo I would much rather see conflicts every time I update, so I haven't done muc

Re: Problems with cygwin cvs over ssh.

> The funny thing is that the > directory in the message *is* created before the commands are even read, > and yet cvs still complains that it can't create it because of ENOENT. I think, that ENOENT is wrong! It should be EEXIST. Perhaps cvs would ignore EEXIST, but now complains about ENOENT. I

Re: Problems with cygwin cvs over ssh.

>> Right. I missed the "." in the original message. The change that >> prompted this behavior seems to be >> . I'm assuming the >> motivation for this patch was to duplicate Linux's behavior (which doesn't >> allow trailing "." in a path pas

Re: Problems with cygwin cvs over ssh.

> > So I guess it's now up to the cvs maintainer to try tracking this down (or > reporting this as a bug upstream). FWIW, I've looked at the sources of > 1.11.17 and didn't see where that "." was added. Did anyone try this with > a test cvs-1.11.21-1? My experience with cvs-1.11.21-1 is that it

Re: Problems with cygwin cvs over ssh.

On Sat, 28 Jan 2006, Corinna Vinschen wrote: > On Jan 27 17:01, Igor Peshansky wrote: > > Ugh, top-posting... Reformatted. > > > > On Fri, 27 Jan 2006, Frank-Michael Moser wrote: > > > > > Igor Peshansky wrote: > > > > > > > The problem is with the CVS server running on Cygwin. CVS in client >

Re: Problems with cygwin cvs over ssh.

On Jan 27 17:01, Igor Peshansky wrote: > Ugh, top-posting... Reformatted. > > On Fri, 27 Jan 2006, Frank-Michael Moser wrote: > > > Igor Peshansky wrote: > > > > > The problem is with the CVS server running on Cygwin. CVS in client > > > mode works just fine. > > > > I have encountered the sam

Re: Problems with cygwin cvs over ssh.

Ugh, top-posting... Reformatted. On Fri, 27 Jan 2006, Frank-Michael Moser wrote: > Igor Peshansky wrote: > > > The problem is with the CVS server running on Cygwin. CVS in client > > mode works just fine. > > I have encountered the same problem, have investigated it a bit and came > out with t

Re: Problems with cygwin cvs over ssh.

I have encountered the same problem, have investigated it a bit and came out with two interesting facts: A) Without changing anything else than replacing cygwin1.dll, using the snaphot cygwin1-20050928.dll works fine while using cygwin1-20050929.dll produces the problem. B) Also without changing

Re: Problems with cygwin cvs over ssh.

On 26/01/06, Igor Peshansky <[EMAIL PROTECTED]> wrote: > > > > Remote CVS server is Solaris, local ssh and Cygwin dll versions are > > latest released. > > Then you have misunderstood the original problem. The problem is with the > CVS server running on Cygwin. CVS in client mode works just fine.

Re: Problems with cygwin cvs over ssh.

On Wed, 25 Jan 2006, René Berber wrote: > Igor Peshansky wrote: > [snip] > > FWIW, I could reproduce the original problem, either with or without > > ":ext:". > > The combination cvs/ssh has no problem : > > $ echo $CVS_RSH > ssh > $ echo $CVSROOT > :ext:[EMAIL PROTECTED]:/export/home0/cvsrep > $

Re: Problems with cygwin cvs over ssh.

Igor Peshansky wrote: [snip] > FWIW, I could reproduce the original problem, either with or without > ":ext:". The combination cvs/ssh has no problem : $ echo $CVS_RSH ssh $ echo $CVSROOT :ext:[EMAIL PROTECTED]:/export/home0/cvsrep $ cvs co junit-test cvs server: Updating junit-test U junit-test/

Re: Problems with cygwin cvs over ssh.

On Wed, 25 Jan 2006, René Berber wrote: > Igor Peshansky wrote: > [snip] > >>From the manual: > >> > >>"If the access method is omitted, then if the repository starts with > >>'/', then :local: is assumed." > >> > >>Try: cvs -d :ext:[EMAIL PROTECTED]:/test-repository co test1 > > > > FWICS, "[EMA

Re: Problems with cygwin cvs over ssh.

Igor Peshansky wrote: [snip] >>From the manual: >> >>"If the access method is omitted, then if the repository starts with >>'/', then :local: is assumed." >> >>Try: cvs -d :ext:[EMAIL PROTECTED]:/test-repository co test1 > > > FWICS, "[EMAIL PROTECTED]" doesn't start with a '/'. "fred" is not i

Re: Problems with cygwin cvs over ssh.

On Wed, 25 Jan 2006, René Berber wrote: > James Courtier-Dutton wrote: > > > CVS_RSH=/bin/ssh > > CVS -d [EMAIL PROTECTED]:/test-repository co test1 > --^^^ > Is this correct? or it was really _cvs_. Both should work unless you use check_case:strict or a shell that does case-sensitive hashing. >

Re: Problems with cygwin cvs over ssh.

James Courtier-Dutton wrote: > CVS_RSH=/bin/ssh > CVS -d [EMAIL PROTECTED]:/test-repository co test1 --^^^ Is this correct? or it was really _cvs_. > ...password > cannot mkdir /tmp/cvs-server1396/. > No such file or directory. > > I am running OpenSSH on a cygwin windows server. > The CVS

Re: Problems with cygwin cvs over ssh.

On Wed, 25 Jan 2006, James Courtier-Dutton wrote: > On 25/01/06, Igor Peshansky xxx wrote: > > On Wed, 25 Jan 2006, James Courtier-Dutton wrote: > > > > > On 25/01/06, Karl-Heinz Wirth <[EMAIL PROTECTED]> wrote: > > > > . Thanks. > > Does anyone

Re: Problems with cygwin cvs over ssh.

On 25/01/06, Igor Peshansky xxx wrote: > On Wed, 25 Jan 2006, James Courtier-Dutton wrote: > > > On 25/01/06, Karl-Heinz Wirth <[EMAIL PROTECTED]> wrote: > > . Thanks. > Does anyone know how to configure gmail to do this? Note: Special manual del

Re: Problems with cygwin cvs over ssh.

On Wed, 25 Jan 2006, James Courtier-Dutton wrote: > On 25/01/06, Karl-Heinz Wirth <[EMAIL PROTECTED]> wrote: . Thanks. > > Hi > > > > >On Wed, 25 Jan 2006, James Courtier-Dutton wrote: > > > > > CVS_RSH=/bin/ssh > > > CVS -d [EMAIL PROTECTED]:/test-rep

Re: Problems with cygwin cvs over ssh.

On 25/01/06, Karl-Heinz Wirth <[EMAIL PROTECTED]> wrote: > Hi > > >On Wed, 25 Jan 2006, James Courtier-Dutton wrote: > > > CVS_RSH=/bin/ssh > > CVS -d [EMAIL PROTECTED]:/test-repository co test1 > > ...password > > cannot mkdir /tmp/cvs-server1396/. > > No such file or directory. > > I am havin

Re: Problems with cygwin cvs over ssh.

Hi >On Wed, 25 Jan 2006, James Courtier-Dutton wrote: > CVS_RSH=/bin/ssh > CVS -d [EMAIL PROTECTED]:/test-repository co test1 > ...password > cannot mkdir /tmp/cvs-server1396/. > No such file or directory. I am having the same problem now, after upgrading to cygwin 1.5.19-4 from 1.5.18-1. I

Re: Problems with cygwin cvs over ssh.

On Wed, 25 Jan 2006, James Courtier-Dutton wrote: > CVS_RSH=/bin/ssh > CVS -d [EMAIL PROTECTED]:/test-repository co test1 > ...password > cannot mkdir /tmp/cvs-server1396/. > No such file or directory. > > I am running OpenSSH on a cygwin windows server. > The CVS repository is on the window

Problems with cygwin cvs over ssh.

Hi, CVS_RSH=/bin/ssh CVS -d [EMAIL PROTECTED]:/test-repository co test1 ...password cannot mkdir /tmp/cvs-server1396/. No such file or directory. I am running OpenSSH on a cygwin windows server. The CVS repository is on the windows server. From CYGWIN: OpenSSH_4.2p1 CVS 1.11.17 So, the p