Re: [fossil-users] Database error after upgrading on Linux

2010-05-11 Thread Wim Paulussen
Dear Heinrich, Thanks for your advise (I have been AWOL for a long time). For the Linux sources no problem, but I rely also on the Windows binaries. The latest available version is 2010-03-18. Is there a release policy regarding the built binaries ? Wim Try to upgrade to a version newer than

[fossil-users] A note and some questions multiple users and fossil

2010-05-11 Thread jim Schimpf
(1) I'm working on a Fossil for Dummies document. I would hope this would be useful to the group as it could be passed to a new user to get them started. It tries to answer the questions of someone just starting out in Fossil. The work can be found at:

Re: [fossil-users] Database error after upgrading on Linux

2010-05-11 Thread Gour
On Tue, 11 May 2010 07:53:16 -0400 Richard == Richard Hipp wrote: Richard Is there a release policy regarding the built binaries ? Richard I'm not sure what you mean by release policy? Fossil is Richard open-source software. You are free to distribute the binaries Richard to whomever you

Re: [fossil-users] Database error after upgrading on Linux

2010-05-11 Thread Richard Hipp
On Tue, May 11, 2010 at 8:46 AM, Gour g...@gour-nitai.com wrote: On Tue, 11 May 2010 07:53:16 -0400 Richard == Richard Hipp wrote: Richard Is there a release policy regarding the built binaries ? Richard I'm not sure what you mean by release policy? Fossil is Richard open-source

[fossil-users] Validating repositories

2010-05-11 Thread Gé Weijers
Hi, Is there any way to get fossil to validate (check the hash) of every single artifact? Ge' ___ 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] Validating repositories

2010-05-11 Thread Richard Hipp
On Tue, May 11, 2010 at 7:39 PM, Gé Weijers g...@weijers.org wrote: Hi, Is there any way to get fossil to validate (check the hash) of every single artifact? fossil test-verify-all Please note that all test-* command are considered debugging commands and are subject to change or removal