Re: [fossil-users] Check your repos! Was: clone/sqlite error
On Thu, Nov 27, 2014 at 2:17 AM, Stephan Beal wrote: > On Thu, Nov 27, 2014 at 12:56 AM, Richard Hipp 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 > trunk copy, then you'll (like me) need to go download a binary to get you > back up an running. > > > I had the same problem on my desktop and on the www.fossil-scm.org server - a single binary of fossil which was compiled from the latest trunk. But Fossil was never broken so badly that I couldn't "fossil update" to a three-week-old working version and recompile. So that's what I did. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Check your repos! Was: clone/sqlite error
On Thu, Nov 27, 2014 at 4:19 AM, Jan Nijtmans wrote: > > A related question: The $HOME/.fossil (or $HOME/_fossil on win32) > and /.fslckout (or /_FOSSIL_) files are sqlite > database files too. Could those become corrupt as well? > In theory, yes. But probably not in practice. Furthermore, the corruption that does occur is merely a misaccounting of free space, not a corruption of actual data, and so is easily cleared by running VACUUM. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Check your repos! Was: clone/sqlite error
[Default] On Wed, 26 Nov 2014 23:39:25 -0800, bch wrote: > On Nov 26, 2014 11:18 PM, "Stephan Beal" 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 Vax/VMS OS did? :P Or use a zfs filesystem with periodic snapshots (timeslider); zfs is available on Illumos, Solaris, FreeBSD, and many Linux distributions (the ZFS on Linux project). -- Regards, Cordialement, Groet, Kees Nuyt ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Check your repos! Was: clone/sqlite error
2014-11-27 8:17 GMT+01:00 Stephan Beal : > 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 for me, except .. My single fossil binary, which _is_ trunk too is configured with --disable-internal-sqlite. Thanks to that I turned out not to be affected ;-) A related question: The $HOME/.fossil (or $HOME/_fossil on win32) and /.fslckout (or /_FOSSIL_) files are sqlite database files too. Could those become corrupt as well? Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Check your repos! Was: clone/sqlite error
On Nov 26, 2014 11:18 PM, "Stephan Beal" wrote: > > On Thu, Nov 27, 2014 at 12:56 AM, Richard Hipp 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 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 :/. Maybe an update script that keeps a .1 .2, .3 version kicking around like the old Vax/VMS OS did? :P > -- > - stephan beal > http://wanderinghorse.net/home/stephan/ > http://gplus.to/sgbeal > "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Check your repos! Was: clone/sqlite error
On Thu, Nov 27, 2014 at 12:56 AM, Richard Hipp 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 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 :/. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Check your repos! Was: clone/sqlite error
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" wrote: > > > On Wed, Nov 26, 2014 at 7:10 PM, bch wrote: > >> On 11/26/14, Richard Hipp 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 *** >> Fragmentation of 102 bytes reported as 0 on page 70508 >> >> That's the one, yes. A simple VACUUM should clear the problem. > > > -- > D. Richard Hipp > d...@sqlite.org > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Check your repos! Was: clone/sqlite error
On Wed, Nov 26, 2014 at 7:10 PM, bch wrote: > On 11/26/14, Richard Hipp 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 *** > Fragmentation of 102 bytes reported as 0 on page 70508 > > That's the one, yes. A simple VACUUM should clear the problem. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Check your repos! Was: clone/sqlite error
On 11/26/14, Richard Hipp 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 --db-check > > If you find a repository that gives errors about an incorrect fragment > count, Is this the error you're speaking of: * /home/bch/work/fossils/fossil.fsl project-name: Fossil repository-size: 112620544 bytes (112.6MB) artifact-count:28013 (stored as 7183 full text and 20830 delta blobs) artifact-sizes:76122 average, 5426487 max, 2132124812 bytes (2.1GB) total compression-ratio: 18:1 checkins: 7647 files: 848 across all branches wikipages: 26 (296 changes) tickets: 1076 (3426 changes) events:5 tagchanges:899 latest-change: 2014-11-26 20:09:19 - about 0 days ago project-age: 2686 days or approximately 7.35 years. project-id:CE59BB9F186226D80E49D1FA2DB29F935CCA0333 database-stats:109981 pages, 1024 bytes/pg, 27351 free pages, UTF-8, delete mode database-check:*** in database main *** Fragmentation of 102 bytes reported as 0 on page 70508 ? > then fix them using: > > fossil sql -R $REPO -cmd vacuum > -- > D. Richard Hipp > d...@sqlite.org > ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Check your repos! Was: clone/sqlite error
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 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 weeks. The official releases are unaffected by the bug. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Check your repos! Was: clone/sqlite error
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 weeks. The official releases are unaffected by the bug. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Check your repos! Was: clone/sqlite error
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: 40005476685d ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Check your repos! Was: clone/sqlite error
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 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 an incorrect fragment count, then fix them using: fossil sql -R $REPO -cmd vacuum http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Check your repos! Was: clone/sqlite error
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 an incorrect fragment count, then fix them using: fossil sql -R $REPO -cmd vacuum ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
