I've finally figured out what was happening. I did indeed have nested
svnroot directories.
When I first started using subversion, I wanted to keep the learning curve
down, so I setup svnserve as a xinetd service and used "-r /svnroot" as a
command line option. Once I got comfortable with running the program, I
switched over to SSH. This happened about a month or two ago and I was
till still using v.1.0.1.
I didn't have any problems switching over to SSH. Which is weird. Since
SSH bypasses xinetd service config files, "svnserve" doesn't get invoked
with the -r option any more, right? Hence the double /svnroot path
segment. However, this problem only surfaced now that I upgraded to
1.0.6. As far as I understand, I should've started seeing the double
svnroot problem as soon as I switched to SSH under 1.0.1. Puzzling...
Dmitry
At 12:50 PM 7/26/2004, Ben Collins-Sussman wrote:
>Try 'svn ls file://svnroot' and look at the repository structure. Or
>use 'svnlook tree /svnroot'. Perhaps somebody moved data around inside
>the repository? Perhaps there really is an 'svnroot' directory *within*
>the repository now?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 27 00:01:56 2004