Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
[bug #45940] CVS cannot connect to remote repo on MSWindows7
9 views
Skip to first unread message
Vincent Belaïche
Sep 12, 2015, 7:19:01 AM9/12/15
to Vincent Belaïche, bug...@nongnu.org
URL:
<http://savannah.nongnu.org/bugs/?45940>
Summary: CVS cannot connect to remote repo on MSWindows7
Project: Concurrent Versions System
Submitted by: vincentb1
Submitted on: sam. 12 sept. 2015 11:18:51 GMT
Category: Bug Report
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Release:
Discussion Lock: Any
Fixed Release: None
Fixed Feature Release: None
_______________________________________________________
Details:
Hello,
Since I have changed my PC from MSW XP to MSW 7, I can no longer use CVS to
access distant repo. However CVS works fine for repo with protocol :local:
I get the following message:
$ cvs -z3 -d:pserver:vinc...@jpicedt.cvs.sourceforge.net:/cvsroot/jpicedt co
-P jpicedt
cvs.exe [checkout aborted]: connect to
jpicedt.cvs.sourceforge.net(216.34.181.112):2401 failed: Connection timed out
I got this same error message above both with CVS version 1.11.22 & 1.12.13a
The cvs I just used to get this error message is that version:
$ cvs --version
Concurrent Versions System (CVS) 1.12.13a (client)
Copyright (C) 2005 Free Software Foundation, Inc.
Senior active maintainers include Larry Jones, Derek R. Price,
and Mark D. Baushke. Please see the AUTHORS and README files from the CVS
distribution kit for a complete list of contributors and copyrights.
CVS may be copied only under the terms of the GNU General Public License,
a copy of which can be found with the CVS distribution kit.
Specify the --help option for further information about CVS
Environment is as follows:
$ env | grep 'CVS\|SVN'
CVSROOT=:local:c:\Users\Vincent\Documents\cvsroot
SVN_SSH=C:/PROGRA~2/PuTTY/plink.exe
CVS_SSH=C:\PROGRA~2\PuTTY\plink.exe
CVS_RSH=C:\PROGRA~2\PuTTY\plink.exe
Please note that:
* SVN is working fine for distant repo using SSH (so PuTTY is not to blame,
AFAI can understand.
* using forward slashes instead of backward slashes does not help
* using the long name "Program Files (x86)" instead of PROGRA~2 does not help
either.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?45940>
_______________________________________________
Message posté via/par Savannah
http://savannah.nongnu.org/
<http://savannah.nongnu.org/bugs/?45940>
Summary: CVS cannot connect to remote repo on MSWindows7
Project: Concurrent Versions System
Submitted by: vincentb1
Submitted on: sam. 12 sept. 2015 11:18:51 GMT
Category: Bug Report
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Release:
Discussion Lock: Any
Fixed Release: None
Fixed Feature Release: None
_______________________________________________________
Details:
Hello,
Since I have changed my PC from MSW XP to MSW 7, I can no longer use CVS to
access distant repo. However CVS works fine for repo with protocol :local:
I get the following message:
$ cvs -z3 -d:pserver:vinc...@jpicedt.cvs.sourceforge.net:/cvsroot/jpicedt co
-P jpicedt
cvs.exe [checkout aborted]: connect to
jpicedt.cvs.sourceforge.net(216.34.181.112):2401 failed: Connection timed out
I got this same error message above both with CVS version 1.11.22 & 1.12.13a
The cvs I just used to get this error message is that version:
$ cvs --version
Concurrent Versions System (CVS) 1.12.13a (client)
Copyright (C) 2005 Free Software Foundation, Inc.
Senior active maintainers include Larry Jones, Derek R. Price,
and Mark D. Baushke. Please see the AUTHORS and README files from the CVS
distribution kit for a complete list of contributors and copyrights.
CVS may be copied only under the terms of the GNU General Public License,
a copy of which can be found with the CVS distribution kit.
Specify the --help option for further information about CVS
Environment is as follows:
$ env | grep 'CVS\|SVN'
CVSROOT=:local:c:\Users\Vincent\Documents\cvsroot
SVN_SSH=C:/PROGRA~2/PuTTY/plink.exe
CVS_SSH=C:\PROGRA~2\PuTTY\plink.exe
CVS_RSH=C:\PROGRA~2\PuTTY\plink.exe
Please note that:
* SVN is working fine for distant repo using SSH (so PuTTY is not to blame,
AFAI can understand.
* using forward slashes instead of backward slashes does not help
* using the long name "Program Files (x86)" instead of PROGRA~2 does not help
either.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?45940>
_______________________________________________
Message posté via/par Savannah
http://savannah.nongnu.org/
Vincent Belaïche
Sep 12, 2015, 5:39:57 PM9/12/15
to Vincent Belaïche, bug...@nongnu.org
Follow-up Comment #1, bug #45940 (project cvs):
FYI, I had first blamed sourceforge, but it proved out that CVS client seems
to be the culprit:
sourceforge ticker #11126
<https://sourceforge.net/p/forge/site-support/11126/>
FYI, I had first blamed sourceforge, but it proved out that CVS client seems
to be the culprit:
sourceforge ticker #11126
<https://sourceforge.net/p/forge/site-support/11126/>
William Silverman
Sep 21, 2015, 4:04:09 PM9/21/15
to Vincent Belaïche, bug...@nongnu.org
Follow-up Comment #2, bug #45940 (project cvs):
I am using CVS version 1.11.23 on my windows 7 cygwin (32 bits) systm, which
btw is fully up-to-date, and version 1.12.13 on my windows XP cygwin system.
The latter works fine and never exhibited the described behavior, while the
former complained of some(?) problem with the public key until I scrubbed it
and reloaded with a clean system. It timed out when I accessed my system
(EFCP) on my Lenovo laptop, as the owner. It did not complain when I accessed
the system on the laptop. as an anonymous user.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?45940>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
I am using CVS version 1.11.23 on my windows 7 cygwin (32 bits) systm, which
btw is fully up-to-date, and version 1.12.13 on my windows XP cygwin system.
The latter works fine and never exhibited the described behavior, while the
former complained of some(?) problem with the public key until I scrubbed it
and reloaded with a clean system. It timed out when I accessed my system
(EFCP) on my Lenovo laptop, as the owner. It did not complain when I accessed
the system on the laptop. as an anonymous user.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?45940>
_______________________________________________
http://savannah.nongnu.org/
Vincent Belaïche
Sep 26, 2015, 4:00:20 PM9/26/15
to Vincent Belaïche, bug...@nongnu.org
Follow-up Comment #3, bug #45940 (project cvs):
Hello,
I think that I have found what was going wrong. In fact I had two problems at
the same time, which made sorthing this out a bit more chalenging.
= My 1st problem =
On my MSW-XP machine, the PuTTY ssh program (aka plink) was there:
C:Program FilesPuTTYplink.exe
and I had configured the envvars like this:
$ @echo CVS_SSH = %CVS_SSH%, CVS_RSH = %CVS_RSH%.
-| CVS_SSH = C:Program FilesPuTTYplink.exe, CVS_RSH = C:Program
FilesPuTTYplink.exe.
and everything was fine, but on my MSW-7 machine, the PuTTY program was
installed there:
C:Program Files (x86)PuTTYplink.exe
and therefore I had accordingly configured the envvars like this:
$ @echo CVS_SSH = %CVS_SSH%, CVS_RSH = %CVS_RSH%.
-| CVS_SSH = C:Program Files (x86)PuTTYplink.exe, CVS_RSH = C:Program Files
(x86)PuTTYplink.exe.
but that was a problem, as I got :
$ cvs -z3 -d:pserver:anon...@jpicedt.cvs.sourceforge.net:/cvsroot/jpicedt
co -P jpicedt
-| cvs.exe [checkout aborted]: connect to
Only the :perserver: protocol is affected by this problem (anonymous access).
The :ext: is fine (authenticated access).
Now this first problem was solved by replacing "Program Files (x86)" by the
equivalent short name, which is "PROGRA~2" in my case, you can know yours by
doing:
$ dir /X C:
-| Le volume dans le lecteur C n'a pas de nom.
-| Le numéro de série du volume est AC5E-0292
-|
-| Répertoire de c:
-|
-| 03/12/2013 22:34 <REP> Drivers
-| 26/09/2015 15:48 <REP> PROGRA~1 Program Files
-| 26/09/2015 15:53 <REP> PROGRA~2 Program Files (x86)
-| 01/07/2014 22:30 <REP> PROGRA~4 Programmes
-| 26/03/2015 14:45 <REP> Users
-| 25/09/2015 10:59 <REP> Windows
-| 0 fichier(s) 0 octets
-| 6 Rép(s) 167 059 132 416 octets libres
So after doing this:
$ @echo CVS_SSH = %CVS_SSH%, CVS_RSH = %CVS_RSH%.
-| CVS_SSH = C:PROGRA~2PuTTYplink.exe, CVS_RSH = C:PROGRA~2PuTTYplink.exe.
and CVS works.
= My 2nd problem =
In fact it was not working in my case neither for authenticated access, nor
for anonymous access, because I had a second problem. As you can read on
Sourceforge CVS doc <https://sourceforge.net/p/forge/documentation/CVS/>,
sourcefore supports CVS up to CVS 1.11.x. However I was using CVS 1.12.13a,
here is what I get with CVS 1.12.13a correctly configures envvars CVS_RSH and
CVS_SSH:
$ cvs -z3 -d:ext:vinc...@jpicedt.cvs.sourceforge.net:/cvsroot/jpicedt co -P
jpicedt
-| cvs.exe [checkout aborted]: reading from server: No such file or directory
error-> Unable to write to standard output: Le canal de communication est sur
le point d'être fermé.
$ cvs -z3 -d:pserver:anon...@jpicedt.cvs.sourceforge.net:/cvsroot/jpicedt
co -P jpicedt
-| cvs.exe [checkout aborted]: connect to
If in addtion the envars are configured with "Program Files (x86)" instead of
"PROGRA~2", which was my initial situation on MSW-7, then I get the same
errors:
$ cvs -z3 -d:ext:vinc...@jpicedt.cvs.sourceforge.net:/cvsroot/jpicedt co -P
jpicedt
-| cvs.exe [checkout aborted]: reading from server: No such file or directory
error-> Unable to write to standard output: Le canal de communication est sur
le point d'être fermé.
$ cvs -z3 -d:pserver:anon...@jpicedt.cvs.sourceforge.net:/cvsroot/jpicedt
co -P jpicedt
-| cvs.exe [checkout aborted]: connect to
Hello,
I think that I have found what was going wrong. In fact I had two problems at
the same time, which made sorthing this out a bit more chalenging.
= My 1st problem =
On my MSW-XP machine, the PuTTY ssh program (aka plink) was there:
C:Program FilesPuTTYplink.exe
and I had configured the envvars like this:
$ @echo CVS_SSH = %CVS_SSH%, CVS_RSH = %CVS_RSH%.
-| CVS_SSH = C:Program FilesPuTTYplink.exe, CVS_RSH = C:Program
FilesPuTTYplink.exe.
and everything was fine, but on my MSW-7 machine, the PuTTY program was
installed there:
C:Program Files (x86)PuTTYplink.exe
and therefore I had accordingly configured the envvars like this:
$ @echo CVS_SSH = %CVS_SSH%, CVS_RSH = %CVS_RSH%.
-| CVS_SSH = C:Program Files (x86)PuTTYplink.exe, CVS_RSH = C:Program Files
(x86)PuTTYplink.exe.
but that was a problem, as I got :
$ cvs -z3 -d:pserver:anon...@jpicedt.cvs.sourceforge.net:/cvsroot/jpicedt
co -P jpicedt
-| cvs.exe [checkout aborted]: connect to
Only the :perserver: protocol is affected by this problem (anonymous access).
The :ext: is fine (authenticated access).
Now this first problem was solved by replacing "Program Files (x86)" by the
equivalent short name, which is "PROGRA~2" in my case, you can know yours by
doing:
$ dir /X C:
-| Le volume dans le lecteur C n'a pas de nom.
-| Le numéro de série du volume est AC5E-0292
-|
-| Répertoire de c:
-|
-| 03/12/2013 22:34 <REP> Drivers
-| 26/09/2015 15:48 <REP> PROGRA~1 Program Files
-| 26/09/2015 15:53 <REP> PROGRA~2 Program Files (x86)
-| 01/07/2014 22:30 <REP> PROGRA~4 Programmes
-| 26/03/2015 14:45 <REP> Users
-| 25/09/2015 10:59 <REP> Windows
-| 0 fichier(s) 0 octets
-| 6 Rép(s) 167 059 132 416 octets libres
So after doing this:
$ @echo CVS_SSH = %CVS_SSH%, CVS_RSH = %CVS_RSH%.
-| CVS_SSH = C:PROGRA~2PuTTYplink.exe, CVS_RSH = C:PROGRA~2PuTTYplink.exe.
and CVS works.
= My 2nd problem =
In fact it was not working in my case neither for authenticated access, nor
for anonymous access, because I had a second problem. As you can read on
Sourceforge CVS doc <https://sourceforge.net/p/forge/documentation/CVS/>,
sourcefore supports CVS up to CVS 1.11.x. However I was using CVS 1.12.13a,
here is what I get with CVS 1.12.13a correctly configures envvars CVS_RSH and
CVS_SSH:
$ cvs -z3 -d:ext:vinc...@jpicedt.cvs.sourceforge.net:/cvsroot/jpicedt co -P
jpicedt
-| cvs.exe [checkout aborted]: reading from server: No such file or directory
error-> Unable to write to standard output: Le canal de communication est sur
le point d'être fermé.
$ cvs -z3 -d:pserver:anon...@jpicedt.cvs.sourceforge.net:/cvsroot/jpicedt
co -P jpicedt
-| cvs.exe [checkout aborted]: connect to
If in addtion the envars are configured with "Program Files (x86)" instead of
"PROGRA~2", which was my initial situation on MSW-7, then I get the same
errors:
$ cvs -z3 -d:ext:vinc...@jpicedt.cvs.sourceforge.net:/cvsroot/jpicedt co -P
jpicedt
-| cvs.exe [checkout aborted]: reading from server: No such file or directory
error-> Unable to write to standard output: Le canal de communication est sur
le point d'être fermé.
$ cvs -z3 -d:pserver:anon...@jpicedt.cvs.sourceforge.net:/cvsroot/jpicedt
co -P jpicedt
-| cvs.exe [checkout aborted]: connect to
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?45940>
_______________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?45940>
_______________________________________________
0 new messages