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

Re: fsverify.py unable to fix invalid svndiff header

From: Steinar Bang <sb_at_dod.no>
Date: Sun, 22 May 2011 00:27:03 +0200

>>>>> Steinar Bang <sb_at_dod.no>:

> I tried adding this to /svn/conf/authz:

> [/trunk/someprog]
> * =

> (everything else in the file are comments)

> But both tools still break at revision 683, which is in the path
> /trunk/someprog/metamodeller.
[snip!]
> I was using the svn+ssh method to access the repo. Do I need http
> access to get the effect you were suggesting?

No I don't. svn+ssh works fine for this.

But I forgot the little part at the start of this page:
 http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html

  "If you're using svnserve, you need to make the authz-db variable
   (within svnserve.conf) point to your access rules file."

So I uncommented this line in the sample svnserve.conf:
# authz-db = authz

And then svnsync pulled the entire repo. Or at least: it didn't stop at
revision 683.

But the resulting repo doesn't seem to be functional:
 sb_at_edwards:~$ svn ls file:///tmp/newrepo/svn/
 sb_at_edwards:~$ svn ls file:///tmp/newrepo/svn/trunk
 svn: URL 'file:///tmp/newrepo/svn/trunk' non-existent in that revision
Received on 2011-05-22 00:27:43 CEST

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.