Hello, I used to have major difficulties cloning huge repositories. (See http://lists.fossil-scm.org:8080/pipermail/fossil-users/2014-May/016234.html).
In that thread the commit http://www.fossil-scm.org/index.html/info/b4dffdac5e706980d911a0e672526ad461ec0640 was brought up as a potential fix. I updated to get the fix and then tried running a clone, and I could indeed get the entire repository. Since then I have discovered that the fix only makes the problem much less likely to happen; I have successfully cloned the netbsd repository a few times, but on the odd occasion I still get: ---------------------------------- Round-trips: 662 Artifacts sent: 0 received: 1970955 Error: Database error: database is locked: {UPDATE event SET mtime=(SELECT m1 FROM time_fudge WHERE mid=objid) WHERE objid IN (SELECT mid FROM time_fudge);} Round-trips: 662 Artifacts sent: 0 received: 1970955 Clone done, sent: 162233 received: 3871283762 ip: X.X.X.X server returned an error - clone aborted ---------------------------------- The annoying thing is that when it fails, it wipes away whatever progress it has made. How difficult would it be to allow fossil to pick up where it left off in such a case? Obviously The Real Fix(tm) is making sure the database error doesn't occur, but I can think of other situations (someone accidentally unplugged a network cable, etc) where one wouldn't want it to delete the progress it has made already. -- Kind Regards, Jan _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
