I'm using the latest tip version of Fossil, and am getting this
complaint on checkins:
Autosync: http://me@server:3691/server
Round-trips: 1 Artifacts sent: 0 received: 0
Pull finished with 343 bytes sent, 716 bytes received
vim "../../ci-comment-B545A069E3EC.txt"
New_Version: ec88709387828f239483256ca8f66f8b1f537c5c
Autosync: http://me@server:3691/server
Round-trips: 1 Artifacts sent: 2 received: 0
Error: Database error: SQL error: database is locked
Round-trips: 1 Artifacts sent: 2 received: 0
Sync finished with 1489 bytes sent, 252 bytes received
Autosync failed.
The odd port number is just a value I picked, the svn port + 1.
The Fossil DB is actually on the server I'm doing the checkin on, but I
switched from a direct file open to an http:// sync when I first started
getting DB locking complaints, thinking that "fossil server" was keeping
the DB locked. But, now that I'm checking in via HTTP, so that
everything goes through the same fossil instance, I don't see who else
could have the DB locked.
The DB is on a local ext3 filesystem, so there shouldn't be anything
going on related to non-POSIX semantics.
This is a newly-converted svn repo, so I can't tell if this is new behavior.
I've killed the background fossil instance and restarted it.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
