Re: Discrepancies in svn mirror created with svnsync

On Wed, Feb 13, 2013 at 08:32:35PM +0000, Philip Martin wrote:
> Stefan Sperling <stsp_at_elego.de> writes:
>
> > It is possible that authz rules prohibit access to the path affected
> > by the revision. In which case svnsync would silently omit that path.
>
> $ svn log -vqr129027 svn://svn.zope.org/repos/main/
> ------------------------------------------------------------------------
> r129027 | (no author) | (no date)
> ------------------------------------------------------------------------
>
> That looks like a revision filtered by authz.

Oh, interesting. I was checking with the web frontend where that
revision looks normal: http://svn.zope.org/?rev=129027&view=rev

When I try a checkout (with my ssh key), it fails with

  $ svn co svn+ssh://svn.zope.org/repos/main/2github/trunk 2github
  svn: E170001: Authorization failed

which pretty much seals the case, I guess.

I'm a bit disconcerned about lack of any warning when svnsync produces a
mirror that is different from the original repository. And also curious
how original first mirror managed to get a copy of that revision, but
not of r129030-129032. Authz rules added after the fact, probably.

I guess I'll have to patch svn-all-fast-export not to segfault when it
encounters such empty revisions. (Unfortunately attempting to exclude
them by revision number is not enough.)

Marius Gedminas

-- 
I never got into Linux. I swear to God, it's only lack of time. I'm past the
years of my life where I can really dig into something like running a Linux
system. I'm very sympathetic to the whole idea; Linux people always think the
way I want to think.
                -- Steve Wozniak