[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

new Debian install "could not connect to server"

From: Anne M. Hammond <hammond_at_txcorp.com>
Date: Thu, 4 Jun 2009 09:54:18 -0600

server subversion 1.4.2
client new Debian install, subversion 1.5.6

       user_at_w3[21] > svn co
https://ice.corp.com/code/pkgs/trunk pkgs
        svn: OPTIONS of 'https://ice.corp.com/code/pkgs/trunk':
        <https://ice.corp.com/code/pkgs/trunk%27:> could not
connect to server (https://ice.corp.com)

The Debian client can telnet to port 443. The user can open the
repository
URL in a browser and authenticate using his svn password, after
accepting
the certificate.

He does not have any auths cached in .subversion/auth/svn.simple.

Would any cached files in the working copy, probably generated when he
checked the repo out under an older version client, prevent the
client from connecting
to the server?

There is nothing in the server log, since there is no connection.

I suggested he check out a fresh copy. I have not heard whether this
worked.
Is there any other troubleshooting that can be done?

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2359479

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-04 17:55:06 CEST

This is an archived mail posted to the Subversion Users mailing list.