On Tue, Jan 14, 2014 at 10:35 PM, Andy Bradford <amb-fos...@bradfords.org>wrote:
> Hello, > > While attempting to pull the Fossil repository, I saw this error: > > $ fossil up > Autosync: https://www.fossil-scm.org/ > Round-trips: 2 Artifacts sent: 0 received: 0 > 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: 2 Artifacts sent: 0 received: 0 > Pull finished with 1346 bytes sent, 1866 bytes received > Autosync failed > The error came from the server, not your local machine. You were not doing a push. But there is some common cleanup code that runs at the end of any pull or push that does the UPDATE command above. The UPDATE is a no-op in the case of a pull, but it runs nevertheless. Probably we should fix that. > > Rerunning the command was successful. Is this normal? I have no other > fossil command running, so the error must have come from remote. > > $ fossil version > This is fossil version 1.28 [4699f8d919] 2014-01-14 10:43:23 UTC > > Thanks, > > Andy > -- > TAI64 timestamp: 4000000052d60237 > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
