On 02/05/14 19:57, Andy Bradford wrote:
>>> Artifacts sent: 0 received: 895 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);} <#key_3_2>
>> [...]
>> As you say, it is highly reproducible, but it requires quite a bit
>> of time to trigger sometimes.
>
> This particular error hasn't come up since this checkin (which didn't
> make it into Fossil 1.28, so it's only in trunk or on branch-1.28):
>
> http://www.fossil-scm.org/index.html/info/b4dffdac5e706980d911a0e672526ad461ec0640
>
> I wonder if you could try again with a build from trunk?
I've been using later versions of fossil for both the NetBSD and
pkgsrc repositories since this discussion took place, and I had one
"{COMMIT}" error, but other than that it has worked great. I'm so happy
to be able to nuke the git repositories I have been using as a work-around.
I'm very, very happy about this fix -- it changes a lot for me
(exclusively to the better).
--
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
