Steven.T.Novakovich@nokia.com wrote:
> Hello svn gurus,
>
> I had an svn repository up and running on an IBM PC
...
> A few days ago the PC was bounced (repeatedly).
> We even lost the kernel routing table entries because
> whoever entered them originally must've only used
>
> route add xxxxx
>
> commands instead of using the /etc/sysconfig/network file.
>
> Anyway, now when we try to, say, do an svn update
> to the main node of our repository tree, an error comes
> back saying:
>
>> svn up
> svn: No repository found in 'svn://172.22.140.131'
>
> But if I do a:
>
> [root@SOLdap svn]# svnlook tree /usr/local/svn
>
> I get all the tree:ed output that I would expect.
> (I'm not going to show it here for the sake of confidentiality.)
...
> So the repository IS there.
>
> So why doesn't [it] work???
Sounds like the same careless person who set up the routing also set up
svnserve.
svnserve was probably running with a different -r (--root) option before the
restart.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 24 11:13:25 2005