Re: [fossil-users] mingw doesn't build anymore on win8-64bit

2013-10-10 Thread Martin Gagnon
On Thu, Oct 10, 2013 at 04:39:03PM +0200, Jan Nijtmans wrote: > 2013/10/10 Jan Nijtmans : > > 2013/10/10 Martin Gagnon : > >> It happens that the only difference between 7 and 8 is the Makefile for > >> mingw which now define: -D_USE_32BIT_TIME_T > > > > This define should only be used for a 32

Re: [fossil-users] mingw doesn't build anymore on win8-64bit

2013-10-10 Thread Martin Gagnon
On Thu, Oct 10, 2013 at 04:39:03PM +0200, Jan Nijtmans wrote: > 2013/10/10 Jan Nijtmans : > > 2013/10/10 Martin Gagnon : > >> It happens that the only difference between 7 and 8 is the Makefile for > >> mingw which now define: -D_USE_32BIT_TIME_T > > > > This define should only be used for a 32

Re: [fossil-users] how to fix links to wiki pages if project name is changed?

2013-10-10 Thread j. van den hoff
On Thu, 10 Oct 2013 20:24:35 +0200, Richard Hipp wrote: On Thu, Oct 10, 2013 at 2:19 PM, j. van den hoff wrote: thanks for clarification. another question which comes up for me for the first time: it seems that either all wiki pages are viewable w/o login or none at all. i.e. there is no

Re: [fossil-users] how to fix links to wiki pages if project name is changed?

2013-10-10 Thread j. van den hoff
On Thu, 10 Oct 2013 20:24:35 +0200, Richard Hipp wrote: On Thu, Oct 10, 2013 at 2:19 PM, j. van den hoff wrote: thanks for clarification. another question which comes up for me for the first time: it seems that either all wiki pages are viewable w/o login or none at all. i.e. there is no

Re: [fossil-users] Breakthrough! [was Re: missing branch tag (?)]

2013-10-10 Thread Andy Bradford
Thus said B Harder on Thu, 10 Oct 2013 11:03:59 -0700: > I was getting "no common ancestor". I too get the warning when using your broken.fsl if I merge into the feature branch from trunk: $ f mer 823ef8 WARNING - no common ancestor: a WARNING - no common ancestor: b WARNING - no common an

Re: [fossil-users] how to fix links to wiki pages if project name is changed?

2013-10-10 Thread Stephan Beal
On Thu, Oct 10, 2013 at 8:21 PM, Stephan Beal wrote: > On Thu, Oct 10, 2013 at 8:19 PM, j. van den hoff < > veedeeh...@googlemail.com> wrote: > >> seems that either all wiki pages are viewable w/o login or none at all. >> i.e. there is no finer-grained access control (e.g. on a per-wiki page >> b

Re: [fossil-users] how to fix links to wiki pages if project name is changed?

2013-10-10 Thread Richard Hipp
On Thu, Oct 10, 2013 at 2:19 PM, j. van den hoff wrote: > > thanks for clarification. another question which comes up for me for the > first time: it seems that either all wiki pages are viewable w/o login or > none at all. i.e. there is no finer-grained access control (e.g. on a > per-wiki page b

Re: [fossil-users] how to fix links to wiki pages if project name is changed?

2013-10-10 Thread Stephan Beal
On Thu, Oct 10, 2013 at 8:19 PM, j. van den hoff wrote: > seems that either all wiki pages are viewable w/o login or none at all. > i.e. there is no finer-grained access control (e.g. on a per-wiki page > basis). is this right? > Correct. > while access-control on a per-page basis might be over

Re: [fossil-users] how to fix links to wiki pages if project name is changed?

2013-10-10 Thread j. van den hoff
On Thu, 10 Oct 2013 14:30:21 +0200, Richard Hipp wrote: On Thu, Oct 10, 2013 at 8:07 AM, j. van den hoff wrote: so the question is, whether on can edit the name/url of existing wiki pages. No. The wiki page name is the primary key used in the low-level artifacts that record wiki pages,

Re: [fossil-users] Breakthrough! [was Re: missing branch tag (?)]

2013-10-10 Thread B Harder
WARNING - no common ancestor: WARNING - no common ancestor: WARNING - no common ancestor: ... On 10/10/13, B Harder wrote: > closed/opened my more complex real-world problem repo and problem still > exists. > > On 10/10/13, B Harder wrote: >> hrmmm... interesting. >> >> I was getting "no com

Re: [fossil-users] Breakthrough! [was Re: missing branch tag (?)]

2013-10-10 Thread B Harder
closed/opened my more complex real-world problem repo and problem still exists. On 10/10/13, B Harder wrote: > hrmmm... interesting. > > I was getting "no common ancestor". > > I closed that repo to mail it. You did you testing (successfully). I > re-opened the repo to replicate my results, and i

Re: [fossil-users] Breakthrough! [was Re: missing branch tag (?)]

2013-10-10 Thread B Harder
hrmmm... interesting. I was getting "no common ancestor". I closed that repo to mail it. You did you testing (successfully). I re-opened the repo to replicate my results, and in fact it worked fine. If you (anybody) have the time, would you create a repo and go through the ~10 steps manually and

Re: [fossil-users] Breakthrough! [was Re: missing branch tag (?)]

2013-10-10 Thread Stephan Beal
On Thu, Oct 10, 2013 at 7:54 PM, Stephan Beal wrote: > This is fossil version 1.27 [4137f4cda9] 2013-09-26 08:09:03 UTC > What led up to that... stephan@tiny:~/tmp/foo$ f co vendor vendor/x vendor/y vendor/z stephan@tiny:~/tmp/foo$ fst repository: /home/stephan/tmp/foo/../broken.fsl local-ro

Re: [fossil-users] Breakthrough! [was Re: missing branch tag (?)]

2013-10-10 Thread Stephan Beal
On Thu, Oct 10, 2013 at 7:31 PM, B Harder wrote: > Breakthrough! > > I have a minimal(ish) example of a repo that is broken: > > Take the attached (broken.fsl, 62K) repo, co [vendor], and try to merge > [trunk]. > i end up with: http://www.wanderinghorse.net/tmp/brad-broke.png which is what i

Re: [fossil-users] mingw doesn't build anymore on win8-64bit

2013-10-10 Thread Jan Nijtmans
2013/10/10 Jan Nijtmans : > 2013/10/10 Martin Gagnon : >> It happens that the only difference between 7 and 8 is the Makefile for >> mingw which now define: -D_USE_32BIT_TIME_T > > This define should only be used for a 32-bit build, never for 64-bit, so > this is indeed a bug. I'll have a look

Re: [fossil-users] mingw doesn't build anymore on win8-64bit

2013-10-10 Thread Jan Nijtmans
2013/10/10 Martin Gagnon : > It happens that the only difference between 7 and 8 is the Makefile for > mingw which now define: -D_USE_32BIT_TIME_T This define should only be used for a 32-bit build, never for 64-bit, so this is indeed a bug. I'll have a look how to fix this. Thanks! Regards,

[fossil-users] mingw doesn't build anymore on win8-64bit

2013-10-10 Thread Martin Gagnon
Hi list.. I recently try to compile latest trunk and the build failed.. Since I was already using a version I compile myself from 1 or 2 month ago, I decide to do a bisect to find which commit break it. So here my bisect result: $ fossil bisect chart

Re: [fossil-users] how to fix links to wiki pages if project name is changed?

2013-10-10 Thread Richard Hipp
On Thu, Oct 10, 2013 at 8:07 AM, j. van den hoff wrote: > so the question is, whether on can edit the name/url of existing wiki > pages. > No. The wiki page name is the primary key used in the low-level artifacts that record wiki pages, so there is no way to change the name after the fact. Thou

Re: [fossil-users] how to fix links to wiki pages if project name is changed?

2013-10-10 Thread j. van den hoff
On Thu, 10 Oct 2013 13:59:28 +0200, Richard Hipp wrote: On Thu, Oct 10, 2013 at 7:54 AM, j. van den hoff wrote: I just stumbled over this: the URL of the "home" wiki page contains the project name as a prefix. if the project names is changed _after_ that wiki page has been created/edited,

Re: [fossil-users] how to fix links to wiki pages if project name is changed?

2013-10-10 Thread Richard Hipp
On Thu, Oct 10, 2013 at 7:54 AM, j. van den hoff wrote: > I just stumbled over this: > > the URL of the "home" wiki page contains the project name as a prefix. if > the project names is changed _after_ that wiki page has been > created/edited, the 'home' link obviously points > somewhere else... I

[fossil-users] how to fix links to wiki pages if project name is changed?

2013-10-10 Thread j. van den hoff
I just stumbled over this: the URL of the "home" wiki page contains the project name as a prefix. if the project names is changed _after_ that wiki page has been created/edited, the 'home' link obviously points somewhere else... I understand that I can fix this by explicitely specifying the