On Thursday 19 February 2004 05:08, Eugene Eric Kim wrote:
> On Thu, Feb 19, 2004 at 04:54:55AM -0500, John Szakmeister wrote:
> > What was your command line to checkout the repository? I'm assumming had
> > setup http://my.server.com/ as the repository itself (using SVNPath).
> > The you changed the configuration to use SVNParentPath? If so, then the
> > location of the repository has moved. Assuming the name of the repo was
> > test, the new URL should be http://my.server.com/test. You need to use
> > svn switch --relocate to rewrite the URL for the working copy.
> svn co http://my.server.com/test
> I deleted the old working copy and started from scratch before I did
> > > What I find very strange about the error message is the first line;
> > > Subversion is trying to access a file in the parent path that doesn't
> > > exist. This same behavior was reported in the other message I cited
> > > above.
> > If you changed the directive and nothing else, then I'd expect to see
> > this as an error. Your working copy still thinks the repository is in
> > the old location.
> I don't think this is the problem, as I'm using a fresh working copy.
> > > * Parent path is /data/svn/repos. I tried both leaving this directory
> > > alone, and also creating a repository in it using svnadmin; both
> > > resulted in the same error. The repository below is /data/svn/test.
> > > I created this using svnadmin.
> > Uh, do you mean the repository below is '/data/svn/repos/test'?
> That's right; sorry.
> > If what I've said doesn't provide any insight, let me know. I've
> > currently got several repositories hosted at home using SVNParentPath and
> > 16 at work... none of which have ever had problems in this configuration.
> Did you create a repository in the parent directory using svnadmin
> create? Based on my understanding of how this all works, it shouldn't
> be necessary, but the docs are a little unclear on this. Neither way
> works for me in any case.
No, your don't need to make the parent directory a repository (and I would
avoid doing that). Here's kind of a script of what I did:
svnadmin create /usr/local/svn/my-repo1
svnadmin create /usr/local/svn/my-repo2
svnadmin create /usr/local/svn/my-repo3
chown -R wwwrun:svn /usr/local/svn/*
This has worked fine for me. Did you make sure to set the permissions on your
Also, have you checked the apache error log at all? It usually has more
information about the error that occurred.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Feb 19 11:38:02 2004