New SVNSYNC bug?
From: David Summers <david_at_summersoft.fay.ar.us>
Date: Mon, 28 Apr 2008 15:38:07 -0500 (CDT)
I've been using 1.5.0 SVNSYNC with WEBDAV proxy since about three days
The last stable version I've been using was r27613 from Nov 2007/11.
A week or so ago I upgraded to 1.5.0 rc3.
Today I was doing some tags and I noticed that the SVNSYNC didn't seem to
That happens evry once in a while and I have to manually do the SVNSYNC
I ran the SVNSYNC manually and it claimed it transferred over the new
I puzzled about that for a few minutes and decided to try to re-initialize
I have a script file which sets up my mirror repositories with
I then ran svnsync on the master like I normally do to populate a new
Now ALL 25 revs showed up with no paths and no messages.
Currently I'm working around the problem by manually copying db/revs and
Once I copy the files manually from master to slave it looks like
If I were guessing, I would guess something to do with SVNSYNC has
I will now proceed to attempt to downgrade back to r27613 and see if the
Any ideas? If I can provide any more information, please let me know. I
Thanks!
-- David Wayne Summers "Linux: Because reboots are for hardware upgrades!" david@summersoft.fay.ar.us PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt PGP Key fingerprint = 0B44 B118 85CC F4EC 7021 1ED4 1516 5B78 E320 2001 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org For additional commands, e-mail: dev-help_at_subversion.tigris.orgReceived on 2008-04-28 22:38:42 CEST |
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.