On 7/18/2014 13:43, Ron W wrote:
Looks like you were asking Fossil to sync one repo against itself.
Yes.
My teammates and I have had no problems preforming CLI operations on a repo also be served by "fossil server".
It doesn't completely fail. The checkins do occur; fossil just gripes about it. (This might be the autosync retry feature at work.)
It may be that SQLite has changed the way it does locking since you tried this. Different OSes also affect the way SQLite does locking.
But, as best I can determine, Fossil won't break anything if you do a CLI commit to a repo being hosted by fossil server.
In principle, Fossil should indeed not care. It should realize this is what's happening and skip the autosync step. But, I'm not going to lobby for it to be fixed. The workaround basically amounts to, "Use Fossil how the docs tell you to, dummy. Don't get cute." :)
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
