Re: Discrepancies in svn mirror created with svnsync

2013-02-14 Thread Daniel Shahaf
Marius Gedminas wrote on Thu, Feb 14, 2013 at 08:28:22 +0200: > On Wed, Feb 13, 2013 at 08:32:35PM +, Philip Martin wrote: > > Stefan Sperling writes: > > > > > It is possible that authz rules prohibit access to the path affected > > > by the revision. In which case svnsync would silently omi

Re: Discrepancies in svn mirror created with svnsync

2013-02-13 Thread Marius Gedminas
On Wed, Feb 13, 2013 at 08:32:35PM +, Philip Martin wrote: > Stefan Sperling 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/ >

Re: Discrepancies in svn mirror created with svnsync

2013-02-13 Thread Philip Martin
Stefan Sperling 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/ r129

Re: Discrepancies in svn mirror created with svnsync

2013-02-13 Thread Stefan Sperling
On Wed, Feb 13, 2013 at 09:19:13PM +0200, Marius Gedminas wrote: > But then I ran svnsync again and it gave me broken revisions again: > > $ svnsync sync file:///$PWD/zope-mirror > $ svnlook author -r 129030 zope-mirror/ | wc -c > 1 > > And then I noticed that r129027 also became broken in

Re: Discrepancies in svn mirror created with svnsync

2013-02-13 Thread Marius Gedminas
On Tue, Feb 12, 2013 at 06:54:14PM +0100, Stefan Sperling wrote: > On Tue, Feb 12, 2013 at 05:18:01PM +0200, Marius Gedminas wrote: > > Anyway, this takes care of prevention. What about recovery? Can I fix > > the three missing revisions manually somehow? > > If you can obtain the original revis

Re: Discrepancies in svn mirror created with svnsync

2013-02-12 Thread Philip Martin
Daniel Shahaf writes: >> The official way of doing this is to dump the repository from r0 >> to rN (using svnadmin dump) and loading this dump file into a freshly >> created repository (svnadmin load). >> Since you're creating an svnsync mirror you should probably run >> 'svnsync init' before loa

Re: Discrepancies in svn mirror created with svnsync

2013-02-12 Thread Daniel Shahaf
Stefan Sperling wrote on Tue, Feb 12, 2013 at 18:54:14 +0100: > On Tue, Feb 12, 2013 at 05:18:01PM +0200, Marius Gedminas wrote: > > Anyway, this takes care of prevention. What about recovery? Can I fix > > the three missing revisions manually somehow? > > If you can obtain the original revision

Re: Discrepancies in svn mirror created with svnsync

2013-02-12 Thread Stefan Sperling
On Tue, Feb 12, 2013 at 05:18:01PM +0200, Marius Gedminas wrote: > Anyway, this takes care of prevention. What about recovery? Can I fix > the three missing revisions manually somehow? If you can obtain the original revision files from the master repository, you can try dropping them into the sl

Re: Discrepancies in svn mirror created with svnsync

2013-02-12 Thread Andreas Mohr
Hi, On Tue, Feb 12, 2013 at 05:18:01PM +0200, Marius Gedminas wrote: > On Sat, Feb 09, 2013 at 11:31:07AM +0100, Andreas Mohr wrote: > > Hi, > > > > On Fri, Feb 08, 2013 at 03:45:29PM +0100, Stefan Sperling wrote: > > > So you should definitely wrap svnsync in a tool like lockfile (part of > > >

Re: Discrepancies in svn mirror created with svnsync

2013-02-12 Thread Marius Gedminas
On Sat, Feb 09, 2013 at 11:31:07AM +0100, Andreas Mohr wrote: > Hi, > > On Fri, Feb 08, 2013 at 03:45:29PM +0100, Stefan Sperling wrote: > > I cannot tell you what happened here and why the revisions in the > > mirro are empty. That sure is concerning. > > > > However there are known race conditi

Re: fsfs.conf knob to have merge() fail rather than automagically rebase Re: Discrepancies in svn mirror created with svnsync

2013-02-09 Thread Daniel Shahaf
Stefan Sperling wrote on Sat, Feb 09, 2013 at 21:19:35 +0100: > On Sat, Feb 09, 2013 at 03:28:02PM +0200, Daniel Shahaf wrote: > > Under the commit finalization lock, if the txn-being-committed's base > > revision is older than the current HEAD, by default the code will commit > > it anyway provide

Re: fsfs.conf knob to have merge() fail rather than automagically rebase Re: Discrepancies in svn mirror created with svnsync

2013-02-09 Thread Stefan Sperling
On Sat, Feb 09, 2013 at 03:28:02PM +0200, Daniel Shahaf wrote: > Under the commit finalization lock, if the txn-being-committed's base > revision is older than the current HEAD, by default the code will commit > it anyway provided that no conflicting changes were made in the interim. > I wonder if

fsfs.conf knob to have merge() fail rather than automagically rebase Re: Discrepancies in svn mirror created with svnsync

2013-02-09 Thread Daniel Shahaf
Andreas Mohr wrote on Sat, Feb 09, 2013 at 11:31:07 +0100: > Hi, > > On Fri, Feb 08, 2013 at 03:45:29PM +0100, Stefan Sperling wrote: > > I cannot tell you what happened here and why the revisions in the > > mirro are empty. That sure is concerning. > > > > However there are known race conditions

Re: Discrepancies in svn mirror created with svnsync

2013-02-09 Thread Andreas Mohr
Hi, On Fri, Feb 08, 2013 at 03:45:29PM +0100, Stefan Sperling wrote: > I cannot tell you what happened here and why the revisions in the > mirro are empty. That sure is concerning. > > However there are known race conditions in svnsync in Subversion 1.6. > See http://subversion.apache.org/docs/re

Re: Discrepancies in svn mirror created with svnsync

2013-02-08 Thread Lathan Bidwell
Zach, the email to unsubscribe is: users-unsubscr...@subversion.apache.org On 02/08/2013 09:47 AM, Zachary Burnham wrote: unsubscribe Z

Re: Discrepancies in svn mirror created with svnsync

2013-02-08 Thread Zachary Burnham
unsubscribe Z [cid:image002.jpg@01CD8139.6DE4E9D0] Zachary Burnham | Web Developer Energy Federation Inc | 1 Willow Street | Southborough, MA 01772 508.870.2277 x4467 | f 888.440.4219 zburn...@efi.org | efi.org On Feb 8, 2013, at 9:45 AM, Stefan

Re: Discrepancies in svn mirror created with svnsync

2013-02-08 Thread Stefan Sperling
On Fri, Feb 08, 2013 at 03:45:16PM +0200, Marius Gedminas wrote: > On Fri, Feb 08, 2013 at 11:44:40AM +0100, Andreas Krey wrote: > > On Thu, 07 Feb 2013 23:00:33 +, Marius Gedminas wrote: > > ... > > > The cron script runs svnsync every 5 minutes. > > > > Do you make sure svnsync isn't starte

Re: Discrepancies in svn mirror created with svnsync

2013-02-08 Thread Thorsten Schöning
Guten Tag Marius Gedminas, am Freitag, 8. Februar 2013 um 14:45 schrieben Sie: > It's possible that a temporal overlap happened. That shouldn't be a problem, as per default svnsync aquires exclusive locks on the destination repo where it should mirror the data to and subsequent calls to svnsync w

Re: Discrepancies in svn mirror created with svnsync

2013-02-08 Thread Marius Gedminas
On Fri, Feb 08, 2013 at 11:44:40AM +0100, Andreas Krey wrote: > On Thu, 07 Feb 2013 23:00:33 +, Marius Gedminas wrote: > ... > > The cron script runs svnsync every 5 minutes. > > Do you make sure svnsync isn't started anew when the previous instance > hasn't terminated yet? (I don't know if t

Re: Discrepancies in svn mirror created with svnsync

2013-02-08 Thread Andreas Krey
On Thu, 07 Feb 2013 23:00:33 +, Marius Gedminas wrote: ... > The cron script runs svnsync every 5 minutes. Do you make sure svnsync isn't started anew when the previous instance hasn't terminated yet? (I don't know if that matters.) Andreas -- "Totally trivial. Famous last words." From: Li

Discrepancies in svn mirror created with svnsync

2013-02-07 Thread Marius Gedminas
I use svnsync to keep a mirror of svn.zope.org. Recently I've noticed that at least three revisions differ between the original and the mirror: http://svn.zope.org/?rev=129030&view=rev http://zope3.pov.lt/trac/changeset/129030 http://svn.zope.org/?rev=129031&view=rev http://zope3.pov.lt/