Re: [fossil-users] Weird cross-contamination between two fossil repositories (and not even talking to server!)

2016-05-27 Thread Eric Rubin-Smith
> On May 27, 2016, at 12:26, Andy Gibbs wrote: > > Hi, > > I've just had a very, very odd experience with fossil. I'm running version > 1.34. > > Let me first explain what I have done. > > I cloned a respository off our server. I then went into the clone's web UI

Re: [fossil-users] Weird cross-contamination between two fossil repositories (and not even talking to server!)

2016-05-27 Thread Ross Berteig
On 5/27/2016 3:58 PM, John P. Rouillard wrote: Hi Richard: Richard Hipp writes: Just to be clear, I consider anything involving shunning to be out-of-the-ordinary. Perfectly reasonable. On that note, does anybody have code for tcl hooks that can be used to reject artifacts that have text

Re: [fossil-users] Weird cross-contamination between two fossil repositories (and not even talking to server!)

2016-05-27 Thread Ron W
On Fri, May 27, 2016 at 6:58 PM, John P. Rouillard wrote: > > On that note, does anybody have code for tcl hooks that can be used to > reject artifacts that have text that matches a particular pattern. The closest Fossil has to this is the "commit permission", which

Re: [fossil-users] Rejected JSON tests

2016-05-27 Thread Stephan Beal
On Fri, May 27, 2016 at 1:39 PM, Kain Abel wrote: > > ./src/cson_amalgamation.c: In function ‘cson_value_new_integer’: > ./src/cson_amalgamation.c:2863:13: warning: dereferencing type-punned > pointer will break strict-aliasing rules [-Wstrict-aliasing] >

Re: [fossil-users] Rejected JSON tests

2016-05-27 Thread Ross Berteig
On 5/27/2016 4:39 AM, Kain Abel wrote: Dear devs, dear users, the script tester.tcl don't like the JSON support?. lm@um:/tmp$ tclsh /tmp/test/tester.tcl /tmp/fossil -quiet -prot can't find package json while executing "package require json" (file "/tmp/test/json.test" line 38)

Re: [fossil-users] Weird cross-contamination between two fossil repositories (and not even talking to server!)

2016-05-27 Thread Richard Hipp
On 5/27/16, Andy Gibbs wrote: > > Ok, a little complicated but nothing too out-of-the-ordinary, I hope. > Just to be clear, I consider anything involving shunning to be out-of-the-ordinary. -- D. Richard Hipp d...@sqlite.org

Re: [fossil-users] Weird cross-contamination between two fossil repositories (and not even talking to server!)

2016-05-27 Thread Stephan Beal
On Fri, May 27, 2016 at 6:39 PM, Andy Gibbs wrote: >File 3rdparty/chromium/third_party/sqlite/sqlite-src-3080704/manifest - > part of check-in [079a920cf4] at 2016-03-13 00:00:00 on branch trunk - ** > message elided ** >File

Re: [fossil-users] Weird cross-contamination between two fossil repositories (and not even talking to server!)

2016-05-27 Thread Andy Gibbs
Hi again, I've just discovered something and maybe it is helpful. I checked the "artifact" webpage for both of these rogue artifacts, and I get multiple sources for the artifact in question, e.g.: http://localhost:8080/artifact/f66f7a17b7 Artifact f66f7a17b78ba617acde90fc810107f34f1a1f2e:

[fossil-users] Weird cross-contamination between two fossil repositories (and not even talking to server!)

2016-05-27 Thread Andy Gibbs
Hi, I've just had a very, very odd experience with fossil. I'm running version 1.34. Let me first explain what I have done. I cloned a respository off our server. I then went into the clone's web UI and disabled the auto-sync feature. I then made 7 commits, the first of which caused a

[fossil-users] Rejected JSON tests

2016-05-27 Thread Kain Abel
Dear devs, dear users, the script tester.tcl don't like the JSON support?. lm@um:/tmp$ ./fossil version -v This is fossil version 1.35 [893905c83e] 2016-05-23 01:05:08 UTC Compiled on May 27 2016 12:36:50 using gcc-5.3.1 20160413 (64-bit) SQLite 3.13.0 2016-05-18 10:57:30 fc49f556e4 Schema