Re: [fossil-users] fossil server gives 403 after upgrade to apache 2.4

On Feb 17, 2017, at 4:05 AM, Benedikt Ahrens wrote: > > after upgrade from apache2.2 to apache2.4, my fossil cgi server gives a > 403 error. Did you read the upgrade guide? https://httpd.apache.org/docs/2.4/upgrading.html Apache 2.4 changes a bunch of things in the

Re: [fossil-users] fast-import crash (mark not declared)

Hi On Thu, 16 Feb 2017 at 14:15 -0800 Ross Berteig wrote: > Sure, we'd all love it if everyone kept their clocks in sync, but in the real > world skew is simply going to happen. In the absence of a central server to > provide the authoritative time stamp, a DVCS like

Re: [fossil-users] fast-import crash (mark not declared)

On 2/17/17, Richard Hipp wrote: > On 2/17/17, Rafal Bisingier wrote: >> >> Shouldn't Fossil at least warn user trying to commit a child wit >> timestamp earlier than parent? > > I think it does that, now. Confirmed: That fix went in 7 years ago:

Re: [fossil-users] fast-import crash (mark not declared)

Hi, On 2017-02-17 at 07:03 -0500 Richard Hipp wrote: >On 2/17/17, Richard Hipp wrote: >> On 2/17/17, Rafal Bisingier wrote: >>> >>> Shouldn't Fossil at least warn user trying to commit a child wit >>> timestamp earlier than parent? >>

Re: [fossil-users] fast-import crash (mark not declared)

On 2/17/17, Rafal Bisingier wrote: > > Out of curiosity: what will happen, when commited parent have timestamp > far away in future? You could move the defective commit onto a branch (a branch named "mistake" is a popular choice). Or you could change the date on the defective

[fossil-users] fossil server gives 403 after upgrade to apache 2.4

Hi, after upgrade from apache2.2 to apache2.4, my fossil cgi server gives a 403 error. It worked fine with apache2.2. The rest of the website works after the upgrade, both over http and https. The apache error log states: [Fri Feb 17 12:00:41.004779 2017] [authz_core:error] [pid 1681] [client

Re: [fossil-users] How to use triggers

On Thu, 16 Feb 2017 21:14:22 -0700 Warren Young wrote: > On Feb 16, 2017, at 6:39 PM, Zoltán Kócsi > wrote: > > > > The itch I want to scratch is what I described: automated > > generation of binaries and documentation on the server at certain > >

Re: [fossil-users] fossil server gives 403 after upgrade to apache 2.4

Addendum: I probably took the original configuration from [1], which would need an update for apache2.4. [1] https://www.fossil-scm.org/xfer/wiki?name=Cookbook#CGI On 02/17/2017 12:05 PM, Benedikt Ahrens wrote: > Hi, > > after upgrade from apache2.2 to apache2.4, my fossil cgi server gives a >

Re: [fossil-users] fast-import crash (mark not declared)

On 2/17/17, Rafal Bisingier wrote: > > Shouldn't Fossil at least warn user trying to commit a child wit > timestamp earlier than parent? I think it does that, now. The timewarps all happened a while ago. -- D. Richard Hipp d...@sqlite.org

Re: [fossil-users] fast-import crash (mark not declared)

Hi On Fri, 17 Feb 2017 at 06:07 -0500 Richard Hipp wrote: > On 2/17/17, Rafal Bisingier wrote: > > > > Shouldn't Fossil at least warn user trying to commit a child wit > > timestamp earlier than parent? > > I think it does that, now. The timewarps all

Re: [fossil-users] fast-import crash (mark not declared)

On Fri, 17 Feb 2017 00:04:29 -0600 Artur Shepilko wrote: > ... > I just realized that the check-in date may be altered via "fossil > amend --date" or from UI via check-in's edit submenu. > This will add the tag "date=" and update the check-ins MTIME. > > Looks like both

Re: [fossil-users] fast-import crash (mark not declared)

Hi, On 2017-02-17 at 07:37 -0500 Richard Hipp wrote: >On 2/17/17, Rafal Bisingier wrote: >> >> Out of curiosity: what will happen, when commited parent have timestamp >> far away in future? > >You could move the defective commit onto a branch (a branch