Thanks Stephan. What solution did you plan to add to the TODO list?
Note that the "is locked" was noticed but there are three possible sqlite3
databases that might be the issue and there are several possible ways that
a db can be locked:
Db's
1. _FOSSIL_ or .fslckout
2. ~/.fossil
3. The private repo db (testing.fossil in my example)
Possible causes of db "Locked"
1. disk or partition full or over quota
2. some previous operation crashed
3. db open by some operation
I still feel that ideally "fossil gdiff" should not tie up the database and
prevent commits but I understand that may not be easy to fix. However
adding the full file name of the actual locked database to the error
message would help a lot.
On Wed, Jul 3, 2013 at 2:11 PM, Stephan Beal <sgb...@googlemail.com> wrote:
> On Wed, Jul 3, 2013 at 11:09 PM, Matt Welland <estifo...@gmail.com> wrote:
>
>> fossil: database is locked: {COMMIT}
>> If the database cannot be freed up during the diff then how about some
>> hint to the user as to what might be going on?
>>
>
> The "is locked" part is the hint, but it's unfortunately well hidden
> within the "rebuild noise" added later on (i don't think that part
> recognizes specific error codes, but i'll add this to the TODO list).
>
>
> --
> ----- stephan beal
> http://wanderinghorse.net/home/stephan/
> http://gplus.to/sgbeal
>
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
--
Matt
-=-
90% of the nations wealth is held by 2% of the people. Bummer to be in the
majority...
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
