On Tue, Jan 14, 2014 at 10:35 PM, Andy Bradford amb-fos...@bradfords.orgwrote:
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
On Wed, Jan 15, 2014 at 6:37 AM, Richard Hipp d...@sqlite.org wrote:
...t 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.
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
On 1/14/14, 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
Thus said B Harder on Tue, 14 Jan 2014 19:38:55 -0800:
No pending commits in other windows? (ie: waiting for you to enter
password for gpg key) ?
No, and in fact, this was the first time I ran any fossil command after
logging in and ps did not show any other fossil commands.
I wonder if
5 matches
Mail list logo