Re: [fossil-users] fossil info on tag & directory: SQLITE_CANTOPEN

On 07/11/2017 06:30 PM, Richard Hipp wrote: On 7/11/17, jungle Boogie wrote: I don't think the -v works: https://www.fossil-scm.org/index.html/help?cmd=info What were you expecting it to do? Your commit is welcomed! Just one minor nitpick here:

Re: [fossil-users] Bug Report: Failure to Recover when Previous Fossil Process got Killed

On 7/11/17, Martin Vahi wrote: > > it would be nice, if the > Fossil were able to recover from that kind of situations > itself, automatically. Fossil *does* recover from situations like this automatically In this case, I don't think the prior fossil command was

Re: [fossil-users] Bug Report Update 1: Failure to Recover when Previous Fossil Process got Killed

On 7/11/17, Martin Vahi wrote: > > The cloning of the remote repository does not > give me all of the files that the remote repository > Web GUI shows to be present. The remote repository URL is: It seems to work when I try this. What files are you missing? > > >

[fossil-users] Bug Report Update 2: Fossil Server side Corrupts if Client Process is Killed

After doing the fossil rebuild at the server side, central repository side, I get the following line at the client side: Fossil internal error: infinite loop in DELTA table citation--start COMMENTS.txt milestone_releases/currently_there_is_none.txt

Re: [fossil-users] Bug Report Update 2: Fossil Server side Corrupts if Client Process is Killed

On 7/11/17, Martin Vahi wrote: > > After doing the > > fossil rebuild > > at the server side, central repository side, > I get the following line at the client side: > > Fossil internal error: infinite loop in DELTA table That is definitely a problem, if it is

Re: [fossil-users] Bug Report Update 2: Fossil Server side Corrupts if Client Process is Killed

On Tue, Jul 11, 2017 at 2:26 PM, Richard Hipp wrote: > Can you start, please, by describing what hardware you are using Related to that: is any repo accessed via a networked drive. (If so, then "don't do that.") -- - stephan beal http://wanderinghorse.net/home/stephan/

Re: [fossil-users] Bug Report Update 1: Failure to Recover when Previous Fossil Process got Killed

On 7/11/17, Martin Vahi wrote: > > If I log into the web GUI of the remote Fossil repository > and use the > > Admin -> Shunned -> Rebuild > > then the web GUI shows me: > > ---citation--start > > SQLITE_ERROR: no such table: ftsidx_segments I think that

[fossil-users] IP address changes for www.fossil-scm.org

Due to upstream infrastructure changes, the IPv4 address for fossil-scm.org is changing. (The IPv6 address will remain the same, I am told.) I *think* I have updated all of the DNS entries correctly and reconfigured the server properly to handle this change. However, the mysteries of Ubuntu are

Re: [fossil-users] diff for browse.c

On 10 July 2017 at 19:19, Warren Young wrote: > On Jul 10, 2017, at 5:56 PM, Richard Hipp wrote: >> >> On 7/10/17, jungle Boogie wrote: >>> Hi All, >>> >>> One very minor update to browse.c to add a comma: >> >> I don't think that

Re: [fossil-users] diff for browse.c

On Jul 11, 2017, at 1:52 AM, Stephan Beal wrote: > > Related trivia: native German speakers, regardless of whether they're > functionally fluent in English, can often be identified in internet forums > via their overuse of commas Another telltale is the implicit subject

Re: [fossil-users] fossil info on tag & directory: SQLITE_CANTOPEN

On 10 July 2017 at 23:32, jungle boogie wrote: > Hi All, > > Maybe this is a bad practice on my part, let me know. > Is that the case with this? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org

Re: [fossil-users] fossil info on tag & directory: SQLITE_CANTOPEN

On Jul 11, 2017, at 12:32 AM, jungle boogie wrote: > > % fossil info stuff > > But that results in this error: > SQLITE_CANTOPEN: cannot open file at line 36100 of [284707a7b3] > SQLITE_CANTOPEN: os_unix.c:36100: (21) > open(/usr/home/jungle/fossil-repos/repo/stuff) -

[fossil-users] Bug Report Update 1: Failure to Recover when Previous Fossil Process got Killed

If I log into the web GUI of the remote Fossil repository and use the Admin -> Shunned -> Rebuild then the web GUI shows me: ---citation--start SQLITE_ERROR: no such table: ftsidx_segments Database Error no such table: ftsidx_segments: { DROP TABLE

Re: [fossil-users] Bug Report Update 1: Failure to Recover when Previous Fossil Process got Killed

On Tue, Jul 11, 2017 at 11:25 AM, Martin Vahi wrote: > > If I log into the web GUI of the remote Fossil repository > and use the > > Admin -> Shunned -> Rebuild > > then the web GUI shows me: > > ---citation--start > > SQLITE_ERROR: no such table:

Re: [fossil-users] diff for browse.c

On Tue, Jul 11, 2017 at 10:33 AM, Aaron Elkins wrote: > > On Jul 11, 2017, at 15:52, Stephan Beal wrote: > > On Tue, Jul 11, 2017 at 4:19 AM, Warren Young wrote: >> >> You are right that commas are often overused, drh. I catch

[fossil-users] Bug Report: Failure to Recover when Previous Fossil Process got Killed

I do not know the exact operation that I killed by the key combination Ctrl-C, but the operation was probably one of the following: fossil addremove or fossil commit or fossil pull or fossil push The result is a "corrupted" repository file with a "locked SQLite" database file.

Re: [fossil-users] diff for browse.c

On Tue, Jul 11, 2017 at 4:19 AM, Warren Young wrote: > You are right that commas are often overused, drh. I catch myself doing > it occasionally. > Related trivia: native German speakers, regardless of whether they're functionally fluent in English, can often be identified

[fossil-users] fossil info on tag & directory: SQLITE_CANTOPEN

Hi All, Maybe this is a bad practice on my part, let me know. I have a directory called stuff and I also have a tag called stuff. Some of the commits are tagged with stuff, so that I can find it easier on the taglist page. This page explains I can find information about the last check-in by

Re: [fossil-users] diff for browse.c

> On Jul 11, 2017, at 15:52, Stephan Beal wrote: > > On Tue, Jul 11, 2017 at 4:19 AM, Warren Young > wrote: > You are right that commas are often overused, drh. I catch myself doing it > occasionally. > > Related

Re: [fossil-users] diff for browse.c

On Jul 11, 2017, at 3:58 PM, Warren Young wrote: > >https://en.wiktionary.org/wiki/actual (noun sense 1) 2! ___ fossil-users mailing list fossil-users@lists.fossil-scm.org

Re: [fossil-users] fossil info on tag & directory: SQLITE_CANTOPEN

On 07/11/2017 04:57 PM, jungle Boogie wrote: On 11 July 2017 at 16:41, Richard Hipp wrote: On 7/11/17, jungle Boogie wrote: Is there at least a workaround in Fossil to report info on a tag if there's a directory with the same name? Using the webapp

Re: [fossil-users] fossil info on tag & directory: SQLITE_CANTOPEN

On 7/11/17, jungle Boogie wrote: > > I don't think the -v works: > https://www.fossil-scm.org/index.html/help?cmd=info > What were you expecting it to do? -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list

Re: [fossil-users] fossil info on tag & directory: SQLITE_CANTOPEN

On 07/11/2017 06:30 PM, Richard Hipp wrote: On 7/11/17, jungle Boogie wrote: I don't think the -v works: https://www.fossil-scm.org/index.html/help?cmd=info What were you expecting it to do? Well that's a good question. With and without the -v seem to produce

Re: [fossil-users] fossil info on tag & directory: SQLITE_CANTOPEN

On 11 July 2017 at 15:14, Warren Young wrote: > On Jul 11, 2017, at 12:32 AM, jungle boogie wrote: >> >> % fossil info stuff >> >> But that results in this error: >> SQLITE_CANTOPEN: cannot open file at line 36100 of [284707a7b3] >> SQLITE_CANTOPEN:

Re: [fossil-users] fossil info on tag & directory: SQLITE_CANTOPEN

On 11 July 2017 at 16:41, Richard Hipp wrote: > On 7/11/17, jungle Boogie wrote: >> >> Is there at least a workaround in Fossil to report info on a tag if >> there's a directory with the same name? Using the webapp I suppose it >> a workaround. >> > >

Re: [fossil-users] fossil info on tag & directory: SQLITE_CANTOPEN

On 7/11/17, jungle Boogie wrote: > > Is there at least a workaround in Fossil to report info on a tag if > there's a directory with the same name? Using the webapp I suppose it > a workaround. > fossil info tag:stuff -- D. Richard Hipp d...@sqlite.org