On Tue, 2011-07-26 at 11:13 +0200, Mario Brandt wrote: > >> This is because the repository format changed slightly between the alpha > >> releases and the beta2 release. You will need to re-create the > >> repository. > >> I had the exact same problem, dump and load into a new repository worked > >> for me. > > The issues are not the repos. I can access my 1.6.17 and older repos > without any issues. > That was the case for me too - I had one repository which I created with alpha2, and load from a dump file. It worked fine with alpha3, and then I saw the error you have with beta2. At the same time, alpha2, alpha3, and beta2 all worked happily with my other repositories, which had been created by svn 1.6.x. I was not using SVNParentPath with these repositories, so can't comment on that, but definitely could not access my alpha2 created repository from beta2 using mod_dav_svn and apache.
Tony > The file system layout is > > /opt/repos <--- ParentPath > /opt/repos/repo1 > /opt/repos/repo2 > /opt/repos/repo3 > /opt/repos/repoN > > As it was in SVN 1.6 SVNParentPath should show a list of the repos > 1,2,3 to N [1] > > > Second of all, don't you get the error documented in > > <http://subversion.apache.org/docs/release-notes/1.7#revprop-packing> in > > that case? > > Nope I don't get that error. This is might related to the mod_dav_svn. > I'm not sure. But at leat I can say that over apache (I don't use > svnserve) I never had an issue with the 1.6.x repos with the > mod_dav_svn 1.7.x apache module. > > Cheers > Mario > > > [1] > http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.serverconfig.httpd.basic -- Tony Butt <t...@cea.com.au> CEA Technologies
