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

On Mon, May 30, 2016 at 4:39 PM, John P. Rouillard wrote: > > In message <38334f96-17cf-e32a-e758-2d15ce5fd...@cheshireeng.com>, > Ross Berteig writes: > >One of the hooks is "command_hook" which is invoked for every > >fossil command. That name can raise an error (or

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

Hi Ross: In message <38334f96-17cf-e32a-e758-2d15ce5fd...@cheshireeng.com>, Ross Berteig writes: >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

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

On Sat, May 28, 2016 at 7:59 AM, Andy Gibbs wrote: > > Thanks, that was exactly the set of answers I was looking for. I now > understand the problem and can avoid it in future. Having done some tests > it > seems that the "fossil rebuild" actually caused the problem --

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

On Fri, May 27, 2016 at 10:00 PM, Stephan Beal wrote: > 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!)

> 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!)

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!)

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] Weird cross-contamination between two fossil repositories (and not even talking to server!)

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!)

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!)

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!)

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