[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #45940] CVS cannot connect to remote repo on MSWindows7

From: Vincent Belaïche
Subject: [bug #45940] CVS cannot connect to remote repo on MSWindows7
Date: Sat, 12 Sep 2015 11:18:52 +0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko


                 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
         Discussion Lock: Any
           Fixed Release: None
   Fixed Feature Release: None




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:vincentb1@jpicedt.cvs.sourceforge.net:/cvsroot/jpicedt co
-P jpicedt
cvs.exe [checkout aborted]: connect to
jpicedt.cvs.sourceforge.net( 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'

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


Reply to this item at:


  Message posté via/par Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]