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

Re: checkout

From: Ryan Schmidt <subversion-2006q2_at_ryandesign.com>
Date: 2006-05-08 17:02:10 CEST

Something you've told us doesn't add up...

On May 8, 2006, at 16:44, Hector Alvarez Pol wrote:

>> Out of curiosity, what's the result of the following?
>> svn ls http://mysite:/mySim1/
> The results is:
> svn ls http://mysite.com:/mySim1/
> mySim1/

Ok. According to this, your repository mySim1 contains only a
directory mySim1. It does not contain a directory trunk, which is why
the command from a previous mail where you tried to check out trunk
failed. There isn't one.

>>> This should be equivalent to:
>>> mkdir simsDir; cd simsDir
>>> svn checkout file:////scratch/hapol/svnroot/trunk mySim1
>>> svn checkout file:////scratch/hapol/svnroot2/trunk mySim2
>>> Does that work? If so, then the problem's in the http access
>>> (which I
>>> suspect), rather than the checkout itself.
> Yes, this works. The problem is only on the http access as you
> mention.

How can that be? We just showed above that the mySim1 repository
(a.k.a. the svnroot repository) contains only a directory mySim1. How
are you now able to check out a directory trunk? What is the result
of the following command?

svn ls file:///scratch/hapol/svnroot

If what you've told us so far is true, then the result should also be
"mySim1/" and the above file-protocol-based checkouts could not have
succeeded. Or perhaps your Apache configuration is not as you told us
it is. Perhaps your Apache setup is looking at a completely different
repository than the one given in the file-protocol-based accesses
above? I'm grasping at straws here, because what you're saying is
happening doesn't make any sense.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 8 17:03:58 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.