Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

2014-05-30 Thread Andy Bradford
Thus said Michai Ramakers on Thu, 29 May 2014 15:35:37 +0200: root@main:/tmp/ftmp# f sync f_f -R r_w Round-trips: 1 Artifacts sent: 0 received: 0 Error: Database error: unable to open database file: {CREATE TEMP TABLE onremote(rid INTEGER PRIMARY KEY);} Round-trips: 1 Artifacts sent: 0

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

2014-05-30 Thread Andy Bradford
Thus said Michai Ramakers on Thu, 29 May 2014 15:35:37 +0200: Can anyone tell what happens under the hood here..? Bingo: http://www.fossil-scm.org/index.html/artifact/d1aef141c961172a1a32f619f339c641cdeaa674?ln=259,268 So it does indeed call ``fossil http'' which will cause fossil to chroot

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

2014-05-30 Thread Michai Ramakers
On 30 May 2014 08:09, Andy Bradford amb-sendok-1404022150.hdbpagcekdcgljghk...@bradfords.org wrote: Thus said Michai Ramakers on Thu, 29 May 2014 15:35:37 +0200: root@main:/tmp/ftmp# f sync f_f -R r_w Round-trips: 1 Artifacts sent: 0 received: 0 Error: Database error: unable to open

Re: [fossil-users] question about parms and ownership of repo vs current/parent dir

2014-05-30 Thread Michai Ramakers
On 30 May 2014 08:24, Andy Bradford amb-sendok-1404023072.eeipjlgjbincchjbb...@bradfords.org wrote: Thus said Michai Ramakers on Thu, 29 May 2014 15:35:37 +0200: Can anyone tell what happens under the hood here..? Bingo:

Re: [fossil-users] libfossil minor milestone: Raspberry Pi

2014-05-30 Thread Stephan Beal
On Fri, May 30, 2014 at 3:36 AM, Warren Young war...@etr-usa.com wrote: PowerPC does some strange things with char, too. You might have fixed that in passing. Very possibly. The bug was that i assumed (despite knowing better, deep down) that (char) is signed, but C does not specify its

Re: [fossil-users] Autosync retry?

2014-05-30 Thread Martin Gagnon
Le 29 mai 2014 16:10, Stephan Beal sgb...@googlemail.com a écrit : Wasn't even aware of pull-only until earlier today. snip Same for me, I always use autosync=1 together with the dont-push=1 setting for that. Look like an option got added by someone that didn't know about the other. --

Re: [fossil-users] Autosync retry?

2014-05-30 Thread Stephan Beal
On Fri, May 30, 2014 at 11:55 AM, Martin Gagnon eme...@gmail.com wrote: Same for me, I always use autosync=1 together with the dont-push=1 setting for that. Look like an option got added by someone that didn't know about the other. LOL - wasn't aware of dont-push, either ;) -- -

[fossil-users] use of 'fossil close'

2014-05-30 Thread Michai Ramakers
Hello, a related issue has come up here at least one: is there any real use for 'fossil close' of a repo? I have only recently started using 'fossil all', and notice that 'fossil all ls -c' (i.e. list checkouts) still show checkout-roots that have been closed. I always used the 'close' command,

[fossil-users] fossil clone on localhost

2014-05-30 Thread Michai Ramakers
Hello, I asked a while ago about apparent slowness when cloning a repo on the localhost (using 'http://localhost/...', because a script happened to work like that). Could anyone give an example of when it makes sense to clone a repo on localhost at all, assuming it ever makes sense..? (I am

Re: [fossil-users] use of 'fossil close'

2014-05-30 Thread Stephan Beal
On Fri, May 30, 2014 at 2:24 PM, Michai Ramakers m.ramak...@gmail.com wrote: a related issue has come up here at least one: is there any real use for 'fossil close' of a repo? Rarely. i can count on one hand the number of times i've used it since 2008. You can get the same effect with: rm -f

Re: [fossil-users] fossil clone on localhost

2014-05-30 Thread Stephan Beal
On Fri, May 30, 2014 at 2:28 PM, Michai Ramakers m.ramak...@gmail.com wrote: Could anyone give an example of when it makes sense to clone a repo on localhost at all, assuming it ever makes sense..? (I am currently i can only think of one (small) reason: to avoid having to know the path to the

Re: [fossil-users] use of 'fossil close'

2014-05-30 Thread Michai Ramakers
On 30 May 2014 14:29, Stephan Beal sgb...@googlemail.com wrote: On Fri, May 30, 2014 at 2:24 PM, Michai Ramakers m.ramak...@gmail.com wrote: I have only recently started using 'fossil all', and notice that 'fossil all ls -c' (i.e. list checkouts) still show checkout-roots that have been

Re: [fossil-users] fossil clone on localhost

2014-05-30 Thread Michai Ramakers
On 30 May 2014 14:28, Michai Ramakers m.ramak...@gmail.com wrote: Could anyone give an example of when it makes sense to clone a repo on localhost at all, assuming it ever makes sense..? (I am currently cleaning up various scripts and dirs here, and a lot of sillyness shows up :) ok, found

Re: [fossil-users] fossil clone on localhost

2014-05-30 Thread Stephan Beal
On Fri, May 30, 2014 at 3:02 PM, Michai Ramakers m.ramak...@gmail.com wrote: ok, found another small reason having to do with permissions, perhaps related with yesterday's thread about permissions. Without looking, I guess tempfiles (journal-related?) are being written in the repo-dir, is

Re: [fossil-users] Autosync retry?

2014-05-30 Thread Ron Wilson
On Fri, May 30, 2014 at 5:55 AM, Martin Gagnon eme...@gmail.com wrote: Le 29 mai 2014 16:10, Stephan Beal sgb...@googlemail.com a écrit : Wasn't even aware of pull-only until earlier today. snip Same for me, I always use autosync=1 together with the dont-push=1 setting for that.

Re: [fossil-users] Autosync retry?

2014-05-30 Thread Andy Bradford
Thus said Ron Wilson on Fri, 30 May 2014 09:42:44 -0400: As I recall, the 2 options have slightly different affects. pull-only only affects auto sync, while dont-push affects both manual and auto sync. A manual push will, of course, still push. ``pull-only'' pertains only to

Re: [fossil-users] use of 'fossil close'

2014-05-30 Thread Stephan Beal
On Fri, May 30, 2014 at 2:29 PM, Stephan Beal sgb...@googlemail.com wrote: That's likely a misinteraction with the all setup and close. When fossil opens a repo db, it automatically records it in the global config db for 'all' purposes. The close command should (but apparently doesn't?)

Re: [fossil-users] fossil clone on localhost

2014-05-30 Thread Ron Wilson
On Fri, May 30, 2014 at 8:30 AM, Stephan Beal sgb...@googlemail.com wrote: On Fri, May 30, 2014 at 2:28 PM, Michai Ramakers m.ramak...@gmail.com wrote: Could anyone give an example of when it makes sense to clone a repo on localhost at all, assuming it ever makes sense..? (I am currently

Re: [fossil-users] libfossil minor milestone: Raspberry Pi

2014-05-30 Thread Stephan Beal
On Fri, May 30, 2014 at 10:20 AM, Stephan Beal sgb...@googlemail.com wrote: On Fri, May 30, 2014 at 3:36 AM, Warren Young war...@etr-usa.com wrote: How much work does this test do compared to normal user operations? Say, a normal checkin, or a pull of the /tree URL from fossil server?

Re: [fossil-users] committing wiki pages changes format parser

2014-05-30 Thread Stephan Beal
On Wed, May 14, 2014 at 5:55 PM, Stephan Beal sgb...@googlemail.com wrote: Would this strategy server your purpose: - add a (-format FORMAT) option to (wiki commit). - if no format is specified, use the format from the prior version (if there is one), defaulting to fossil-wiki if no prior

[fossil-users] working checkout does not match what would have ended up in the repository

2014-05-30 Thread Michai Ramakers
Hello, some weirdness I have not seen before: michai@main:~/proj/081/adm$ f changes ADDED time_spent.txt ADDED ../comm/20140530_sent_to_ec/indicator-B_Cu.pho ADDED ../comm/20140530_sent_to_ec/indicator-B_Mask.pho ADDED ../comm/20140530_sent_to_ec/indicator-Edge_Cuts.pho ADDED

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-30 Thread Michai Ramakers
and... michai@main:~/proj/081$ f timeline +++ no more data (0) +++ This is a brand new repo; indeed there are no checkins. Michai On 30 May 2014 21:06, Michai Ramakers m.ramak...@gmail.com wrote: Hello, some weirdness I have not seen before: michai@main:~/proj/081/adm$ f changes ADDED

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-30 Thread Richard Hipp
Is the offending file a symbolic link? On Fri, May 30, 2014 at 3:11 PM, Michai Ramakers m.ramak...@gmail.com wrote: and... michai@main:~/proj/081$ f timeline +++ no more data (0) +++ This is a brand new repo; indeed there are no checkins. Michai On 30 May 2014 21:06, Michai Ramakers

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-30 Thread Michai Ramakers
On 30 May 2014 21:13, Richard Hipp d...@sqlite.org wrote: Is the offending file a symbolic link? no: -rw-r--r-- 1 michai users 163 May 30 20:42 time_spent.txt nor are there any symlinks in the path leading to the file or repo. If interested: the repo is about 53 kB; I could mail it for

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-30 Thread Michai Ramakers
On 30 May 2014 21:13, Richard Hipp d...@sqlite.org wrote: Is the offending file a symbolic link? I don't think it's the contents of this or the other files causing this: michai@main:~/proj/081$ echo kiwi kiwi michai@main:~/proj/081$ f add kiwi ADDED kiwi michai@main:~/proj/081$ f ci -m

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-30 Thread Richard Hipp
On Fri, May 30, 2014 at 3:23 PM, Michai Ramakers m.ramak...@gmail.com wrote: On 30 May 2014 21:13, Richard Hipp d...@sqlite.org wrote: Is the offending file a symbolic link? I don't think it's the contents of this or the other files causing this: michai@main:~/proj/081$ echo kiwi kiwi

Re: [fossil-users] libfossil minor milestone: Raspberry Pi

2014-05-30 Thread Warren Young
On 5/30/2014 11:23, Stephan Beal wrote: a) pi is using an external USB 2.0 drive here because compiling anything on a SD card is just too pokey. Rotating media or SSD? Did you use the same external HDD on the laptop, or did it have an unfair advantage in its internal drive? b) These

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-30 Thread Michai Ramakers
On 30 May 2014 21:27, Richard Hipp d...@sqlite.org wrote: The proximal cause of the error message is the pre-commit sanity checks that Fossil runs on each check-in. (See http://www.fossil-scm.org/fossil/doc/tip/www/selfcheck.wiki for details.) Fossil is looking at the files it is about to

Re: [fossil-users] libfossil minor milestone: Raspberry Pi

2014-05-30 Thread Stephan Beal
On Fri, May 30, 2014 at 9:33 PM, Warren Young war...@etr-usa.com wrote: On 5/30/2014 11:23, Stephan Beal wrote: a) pi is using an external USB 2.0 drive here because compiling anything on a SD card is just too pokey. Rotating media or SSD? Plain old cheap spinning disk. i don't want to

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-30 Thread Stephan Beal
On Fri, May 30, 2014 at 9:11 PM, Michai Ramakers m.ramak...@gmail.com wrote: michai@main:~/proj/081$ f timeline +++ no more data (0) +++ This is a brand new repo; indeed there are no checkins. *cough* this looks _exactly_ like a bug we had recently involving the rid 0 (no checkins) case. i

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-30 Thread Stephan Beal
On Fri, May 30, 2014 at 9:23 PM, Michai Ramakers m.ramak...@gmail.com wrote: On 30 May 2014 21:13, Richard Hipp d...@sqlite.org wrote: Is the offending file a symbolic link? I don't think it's the contents of this or the other files causing this: michai@main:~/proj/081$ echo kiwi kiwi

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-30 Thread Michai Ramakers
On 30 May 2014 22:25, Stephan Beal sgb...@googlemail.com wrote: On Fri, May 30, 2014 at 10:15 PM, Stephan Beal sgb...@googlemail.com wrote: Is this repo _completely_ empty (no initial checkin)? If so, please recreate it with an initial empty checkin and i'll bet my left leg the problem goes

Re: [fossil-users] use of 'fossil close'

2014-05-30 Thread Michai Ramakers
On 30 May 2014 18:43, Stephan Beal sgb...@googlemail.com wrote: On Fri, May 30, 2014 at 2:29 PM, Stephan Beal sgb...@googlemail.com wrote: That's likely a misinteraction with the all setup and close. When fossil opens a repo db, it automatically records it in the global config db for 'all'

Re: [fossil-users] use of 'fossil close'

2014-05-30 Thread Stephan Beal
No hurry - i won't be back on the pc until tomorrow evening. The wife's attention takes priority, in any case! If at first I don't succeed... my wife will never let me forget it. (recently heard in a video game) (sent from a mobile device - please excuse brevity, typos, and top-posting) -

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-30 Thread Andy Bradford
Thus said Michai Ramakers on Fri, 30 May 2014 21:06:36 +0200: michai@main:~/proj/081/adm$ f ci -m 'added note about spent time' time_spent.txt New_Version: 187aa4a7c8b1377ddf05b1d979afe89adeff8dc0 working checkout does not match what would have ended up in the repository:

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-30 Thread Andy Bradford
Thus said Stephan Beal on Fri, 30 May 2014 22:25:30 +0200: H. It seems fossil no longer has an option to create the initial checkin. It does using the --date-override option: fossil new --date-override '2014-05-30 00:00:00' test.fossil Will create a new fossil with an initial empty

[fossil-users] working with open source code

2014-05-30 Thread Abilio Marques
Hi, Let's say I want to do this setup: Clone sqlite repo on a local server Then clone the server into several machines, with the users pushing changes Then, someday, I will want to update my sqlite base code. In git, one would first fork the code from another repo, add a second remote: git

Re: [fossil-users] working with open source code

2014-05-30 Thread B Harder
IIUC: you: fossil clone http://sqlite.org:8080 fossils/sqlite.fsl; cd project_dir; fossil open ~/project_dir/sqlite.fsl; fossil server Each of your our co-conspirators: fossil clone http://your.machine.address:8080 fossils/sqlite.fsl; cd project_dir; fossil open ~/fossils/sqlite.fsl You will: