[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:41:14 +0200

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

>>>>> Steinar Bang <sb_at_dod.no>:
>> I tried adding this to /svn/conf/authz:

>> [/trunk/someprog]
>> * =

>> (everything else in the file are comments)
[snip!]
> 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

More fine print I didn't read, in:
 http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html

  "By default, nobody has any access to the repository at all. That
   means that if you're starting with an empty file, you'll probably
   want to give at least read permission to all users at the root of the
   repository."

So now the /svn/conf/authz file contains:
[/]
* = r

[/trunk/someprog]
* =

And then I'm able to see contents in the cloned repository:
 sb_at_edwards:~$ svn ls file:///tmp/newrepo/svn/
 branches/
 tags/
 trunk/

Thanks, Daniel!
Received on 2011-05-22 00:41:55 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.