It looks like some weird artifacts left over from CVS.

It took a day or two to tweak all the setting for the initial conversion, I 
thought I had successfully filtered all the stuff that wouldn't convert 
properly.  There were quite a few tags and branches which were worthless, the 
various hand edits to CVS caused a few bad things to happen during the 
migration process.

I would except Trac to die if it was really repos corruption, Trac tends to be 
pretty sensitive to SVN issues.

To attempt to diagnose this issue would mean bringing the BOINC website down 
during the recovery process.

Can svnsync be told to skip certain transactions?

----- Rom

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Nicolás Alvarez
Sent: Thursday, December 10, 2009 11:31 PM
To: BOINC Developers Mailing List
Subject: [boinc_dev] Corrupted SVN repository?

http://boinc.berkeley.edu/trac/changeset/6540

Revisions 6540-6543 are weird. Log message shows they are from the
cvs2svn process. They seem to delete everything from trunk, which is
impossible: r6541 can't delete a file if r6540 already did exactly
that, and then how does r6544 edit the stuff that was deleted?

Trying to run svnsync on the BOINC repository halts at revision 6540
with "svnsync: '/branches/unlabeled-1.29.12/boinc_papers' is out of
date". I'm pretty sure svnsync was working fine a few months ago.

In addition, those "unlabeled" branches seem quite empty. boinc/client
in the branch contains a single file, for example.

Any idea what this is about?

-- 
Nicolas
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to