2014-11-27 8:17 GMT+01:00 Stephan Beal sgb...@googlemail.com:
And if you (like me) only have a single fossil binary which _is_ that trunk
copy, then you'll (like me) need to go download a binary to get you back up
an running.
One of these days i'll learn to keep a backup binary :/.
The same
[Default] On Wed, 26 Nov 2014 23:39:25 -0800, bch
brad.har...@gmail.com wrote:
On Nov 26, 2014 11:18 PM, Stephan Beal sgb...@googlemail.com wrote:
One of these days i'll learn to keep a backup binary :/.
Maybe an update script that keeps a .1 .2, .3 version kicking
around like the old
On Thu, Nov 27, 2014 at 4:19 AM, Jan Nijtmans jan.nijtm...@gmail.com
wrote:
A related question: The $HOME/.fossil (or $HOME/_fossil on win32)
and ckout-dir/.fslckout (or ckout-dir/_FOSSIL_) files are sqlite
database files too. Could those become corrupt as well?
In theory, yes. But
On Thu, Nov 27, 2014 at 2:17 AM, Stephan Beal sgb...@googlemail.com wrote:
On Thu, Nov 27, 2014 at 12:56 AM, Richard Hipp d...@sqlite.org wrote:
No. This only applies if you are downloading the latest source code from
trunk and compiling it yourself, and have done so in the past couple of
If you have been using the latest trunk versions of Fossil, you should:
(1) Recompile with the very latests
(2) Check all of your repositories for possible corruption. You can do
this easily using the command:
fossil all dbstat --db-check
If you find a repository that gives errors about
Is this on version 1.29 [3e5ebe2b90] 2014-06-12 17:25:56 UTC?
- Original Message -
From: Richard Hipp
To: Fossil SCM user's discussion
Sent: Wednesday, November 26, 2014 6:40 PM
Subject: [fossil-users] Check your repos! Was: clone/sqlite error
If you have been using
Thus said Richard Hipp on Wed, 26 Nov 2014 18:40:19 -0500:
If you find a repository that gives errors about an incorrect fragment
count, then fix them using:
Thanks, apparently my Fossil fossil had an incorrect fragment count, no
others.
It now reports ok.
Andy
--
TAI64 timestamp:
On Wed, Nov 26, 2014 at 6:53 PM, jose isaias cabrera
jic...@cinops.xerox.com wrote:
Is this on version 1.29 [3e5ebe2b90] 2014-06-12 17:25:56 UTC?
No. This only applies if you are downloading the latest source code from
trunk and compiling it yourself, and have done so in the past couple of
Perfect! thanks.
- Original Message -
From: Richard Hipp
To: Fossil SCM user's discussion
Sent: Wednesday, November 26, 2014 6:56 PM
Subject: Re: [fossil-users] Check your repos! Was: clone/sqlite error
On Wed, Nov 26, 2014 at 6:53 PM, jose isaias cabrera
jic
On 11/26/14, Richard Hipp d...@sqlite.org wrote:
If you have been using the latest trunk versions of Fossil, you should:
(1) Recompile with the very latests
(2) Check all of your repositories for possible corruption. You can do
this easily using the command:
fossil all dbstat
On Wed, Nov 26, 2014 at 7:10 PM, bch brad.har...@gmail.com wrote:
On 11/26/14, Richard Hipp d...@sqlite.org wrote:
If you find a repository that gives errors about an incorrect fragment
count,
Is this the error you're speaking of:
database-check:*** in database main ***
I had 3 affected repos, according to the stats. I ran the vacuum on them,
and they're fixed, again, according to the stats.
On Nov 26, 2014 5:09 PM, Richard Hipp d...@sqlite.org wrote:
On Wed, Nov 26, 2014 at 7:10 PM, bch brad.har...@gmail.com wrote:
On 11/26/14, Richard Hipp d...@sqlite.org
On Thu, Nov 27, 2014 at 12:56 AM, Richard Hipp d...@sqlite.org wrote:
No. This only applies if you are downloading the latest source code from
trunk and compiling it yourself, and have done so in the past couple of
weeks.
And if you (like me) only have a single fossil binary which _is_ that
On Nov 26, 2014 11:18 PM, Stephan Beal sgb...@googlemail.com wrote:
On Thu, Nov 27, 2014 at 12:56 AM, Richard Hipp d...@sqlite.org wrote:
No. This only applies if you are downloading the latest source code
from trunk and compiling it yourself, and have done so in the past couple
of weeks.
14 matches
Mail list logo
