> Steinar Bang :
> Steinar Bang :
>> 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
> Steinar Bang :
> 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.
> Daniel Shahaf :
> Steinar Bang wrote on Sat, May 21, 2011 at 18:26:30 +0200:
[snip! svnsync and svnrdump]
>> .., it would have been nice if it was possible to tell these tools to
>> make a clone of a particular part of the repository into a new
>> repository (or a dumpfile for that matter).
Am 21.05.2011 19:12, schrieb Daniel Shahaf:
Does http://subversion.tigris.org/issues/show_bug.cgi?id=3884 describe
the problem you were seeing?
Yes. But I wonder why file sees a text file for you. In the repository
where I do the merge I see a symlink. I get a normal file only after a
new c
Ulrich Eckhardt wrote on Thu, May 19, 2011 at 10:55:59 +0200:
> On Wednesday 18 May 2011, Christian Gils wrote:
> > I've version 1.5.6 using FSFS stored on ext3 (RHEL 5.4). The repository
> > contains about 39k revisions. Revisions 0-36672 are fine and dump
> > without any problems. Revisions 36673
Does http://subversion.tigris.org/issues/show_bug.cgi?id=3884 describe
the problem you were seeing?
Christoph Bartoschek wrote on Thu, May 19, 2011 at 11:12:01 +0200:
> Hi,
>
> do I have to open an issue for this?
>
> Am 17.05.2011 13:24, schrieb Daniel Shahaf:
> >I committed
> >
> >http://svn.a
svnsync,svnrdump use the svn_ra_* API, not the svn_client_* API.
You should be able to use either of them if you install authz on your
repository such that *any* paths touched in r683 are unreadable by the
user svnsync/svnrdump connect as.
Steinar Bang wrote on Sat, May 21, 2011 at 18:26:30 +0200
> Steinar Bang :
> I've been looking to see if there are any tools that can slurp out the
> history of a repository, using the svn client API. But all repository
> conversion seems to be based on "svnadmin dump". And "svnadmin dump"
> croaks on all revisions later than 682...:-/
svnsync and
Try figuring out what the error number is.
(the error text comes from apr_os_strerror(), see there for pointers on
how to interpret the error number)
Daniel wrote on Thu, May 19, 2011 at 18:12:10 -0300:
> In a working repository, I started to having the following error message:
>
> Commit
> Comm
