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 ser
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
Hi,
I am confused by fossil ignore and clean behaviour.
I have a lot of files, recognizable by extension, that I would like to
ignore when calling fossil status (1), but delete when calling fossil
clean (2).
For (1), I had put a pattern in ignore-glob. Realizing that they would
not be cleaned
On Mon, Aug 5, 2013 at 10:15 PM, Richard Hipp d...@sqlite.org wrote:
On Mon, Aug 5, 2013 at 3:55 PM, Benedikt Ahrens
benedikt.ahr...@gmx.netwrote:
is not feasible in my situation.
packages or libraries or deal with package managers. Just copy *one file*
into your $PATH on each machine
Hello,
the fossil timeline command shows UTC time rather than observing the
system setting (UTC+02:00, in my case).
Is there anything I can do to change this?
fossil version is 1.26.
Thanks.
Benedikt
___
fossil-users mailing list
Hello,
thanks a lot for your answers.
The repository in question is a bit less than 100MB big and carries
around 30 binaries of up to 6MB each.
I am aware that the fossil version I am using is outdated, but as Joseph
said, it is the version packaged in Debian stable, and in Ubuntu 12.04
as
Hello,
I am having trouble with a fossil repository containing many binary files.
Firstly, after cloning I only have the first (empty) commit in the
timeline, even though many commits have been made to the cloned repository:
$ fossil timeline
=== 2013-08-01 ===
13:06:56 [c497b616a3] *CURRENT*
Dear all,
since today I am experiencing problems with my fossil repositories:
I can clone and update from the fossil repo on my server, but not write
to it:
$ fossil ci -m added test textfile
Autosync: http://user@server/r.cgi/ba
Bytes Cards Artifacts Deltas
Sent:
I've accidentally set it to 640 instead of 660.
Thanks,
Kevin
Sent from my iPhone
On 19 Jun 2012, at 18:59, Benedikt Ahrens benedikt.ahr...@gmx.net wrote:
Dear all,
since today I am experiencing problems with my fossil repositories:
I can clone and update from the fossil repo on my
9 matches
Mail list logo
