Re: [fossil-users] Fossil SCGI Server Regression (from 1.36 to 1.37)

[Thomas Bilk]

So I did bisect yesterday and oh wonder, everything worked properly. I
don't know why I had an issue on Sunday but today it works on a new
test server as well as on my production server. So all-clear for the
server --scgi command.

I would like to use the occasion to thank you developers of fossil
again for this magnificent piece of software. I have to use git at
work which is a mess and I am so happy that I can use a good source
control system for all my project. So, thank you again.

Best regards.
Thomas.

> 2017-02-13 0:28 GMT+01:00 Richard Hipp :
>>> I guess there was a regression introduced somewhere between [8b03934e]
>>> and [fb4b87d9].
>>
>> Would you be willing to bisect for us?
>
> Sure. I will report my findings later today.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fossil SCGI Server Regression (from 1.36 to 1.37)

[Thomas Bilk]

2017-02-13 0:28 GMT+01:00 Richard Hipp :
>> I guess there was a regression introduced somewhere between [8b03934e]
>> and [fb4b87d9].
>
> Would you be willing to bisect for us?

Sure. I will report my findings later today.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Fossil SCGI Server Regression (from 1.36 to 1.37)

[Thomas Bilk]

Hi all.

I was finally upgrading my fossil server and encountered what I assume
to be a regression. I am using the fossil server with scgi behind an
nginx web server. I am hosting a directory with fossil repositories.
These is my configuration:

The fossil server is started with this
fossil server --localhost --scgi --port 12001 /var/repos

The nginx config:
server {
  listen80;
  location / {
include scgi_params;
scgi_pass   localhost:12001;
scgi_param  SCRIPT_NAME "";
  }
}

Until version 1.36 I could access my projects on from the “/var/repos”
folder like this: “http://myserver.com/myrepo”. When I upgraded my
fossil binary to version 1.37 [fb4b87d9] this does not seem to work
any more.

I got it to work partially by adding the “--baseurl
http://myserver.com/” parameter to the fossil call and configuring
nginx to use “scgi_param  PATH_NAME $fcgi_path_name;”. But that always
led to a redirect when I called the URL from above to
“http://myserver.com//myrepo/index” with an additional slash.

I guess there was a regression introduced somewhere between [8b03934e]
and [fb4b87d9]. I am currently sticking with the older version but
would love to upgrade.

Best regards,
Thomas.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Merge failed with SQL error

[Thomas Bilk]

I have had the same issue with a merge with versions 1.35, 1.36 and a
recent trunk build. I finally managed to merge my branches with
version 1.34 of Fossil. So I guess the problem might stem from the
`merge-renames` branch
(http://fossil-scm.org/index.html/timeline?t=merge-renames), that
happened in May 2016.

What's odd is that my merge did not contain any renames. However
before I had the SQLITE_CONSTRAINT error, the merge tried to delete a
file that existed in both branches.

I guess I can offer access to the afflicted repository if someone
wants to peek into it.

Thanks.
Thomas.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Version 1.33

[Thomas Bilk]

I managed to recreate the problem in Opensuse 13.2 maybe there is a
problem there. I have created a Dockerfile that sets up OpenSuse so
that fossil can be built and run. The problem is the same as on my
machine. So here is the Dockerfile:[http://pastebin.com/4tB0ZR85]

If you already have Docker installed all you need to run are these
commands in the Folder where the Dockerfile is:

docker build --tag fossil_reports_opensuse .
docker run --rm --name fossil_reports_opensuse -p 8080:8080
fossil_reports_opensuse

Then try to access the address http://{{ docker ip }}:8080/reports and
see no response.

Meanwhile I managed to build fossil in OpenSuse if I removed -O2 from
the Makefile.

On Mon, Jun 1, 2015 at 11:57 PM, Richard Hipp d...@sqlite.org wrote:

 Can you offer any suggestions on how I can recreate the problem, so
 that I can try to figure out what is going wrong?

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Version 1.33

[Thomas Bilk]

I also cannot access the /reports url. When I curl the address I get
an empty reply from the server. Does Fossil have some kind of error
log?
I am using the checkout [2b1261a59] with gcc 4.8.3 on OpenSuse.

On Thu, May 28, 2015 at 7:06 PM, Richard Hipp d...@sqlite.org wrote:
 On 5/28/15, Svyatoslav Mishyn j...@openmailbox.org wrote:
 (Wed, 27 May 14:03) Warren Young:
 On May 23, 2015, at 1:25 PM, Svyatoslav Mishyn j...@openmailbox.org
 wrote:
 
  /tmp: wget -S http://localhost:8080/reports
  --2015-05-23 21:42:12--  http://localhost:8080/reports
  Resolving localhost (localhost)... 127.0.0.1
  Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
  HTTP request sent, awaiting response... No data received.
  Retrying.

 That works here.

 Finally, I found why ;)
 It is just  CFLAGS=' -O2'.


 (and if it matters: Clang - 3.6.0; GCC - 4.8.4

 + if Clang:
 ./src/rss.c:99:40: warning: address of 'g.perm.Read' will always evaluate to
 'true' [-Wpointer-bool-conversion]
   assert( !g.perm.RdTkt  g.perm.Read  g.perm.RdWiki );

 Three  characters instead of two.  Fixed in the latest check-in.

 ~~  ~~~^~~~
 /usr/include/assert.h:86:5: note: expanded from macro 'assert'
   ((expr)   \
 ^
 1 warning generated.


 and of course much more warnings with CFLAGS=' -ansi -pedantic -Wall
 -Wextra'
 )


 Should I add `unset CFLAGS` to  Pkgfile?


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Email notification on ticket creation or modification

[Thomas Bilk]

This can be achieved even easier as I discovered just recently. There is
a rss command option for fossil that generates rss files. I use this
bash script with a cron to generate all rss files to a public directory:

#!/usr/bin/env bash
for fos in `ls /var/repos/*.fossil`; do
  rss=`echo $fos | sed 's/\/var\/repos\/\(.*\)\.fossil/\1/'`;
  /usr/local/bin/fossil rss -R $fos --url https://repos.com/$rss 
/var/public/rss/$rss.rss;
done

Am 31.07.2014 18:40, schrieb Stephan Beal:
 On Thu, Jul 31, 2014 at 5:49 PM, James Bremner ja...@ravenspoint.com
 mailto:ja...@ravenspoint.com wrote:
 
 On 28/07/2014 2:24 PM, Ross Berteig wrote:
 
 all the RSS-based services I could find could not do authentication
 
 
 How about a cron job which uses wget::
 
 wget http://me:mypassword@myrepo/timeline.rss -O thefeed.rss
 
 and maybe then feed that feed file to your non-auth-capable reader?
 
 -- 
 - stephan beal
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] looking for interesting new fossil skins

[Thomas Bilk]

Am 14.02.2014 11:02, schrieb Samuel Debionne:
 Hi Stephen,
 
 I have made a skin using Twitter Bootstrap CSS that looks quite good
 IMHO (responsive layout and all). Actually this is a bit more involving
 than just using the skin, it requires patching the markup that is
 generated by fossil a bit, something that I maintain in my private
 branch (but I would love to have this in the master if acceptable !).
 The patch mainly add classes (something that could be probalby done non
 intruively using javascript) and change tables for divs when tables are
 used for the layout.

Hi all.

The Skin looks really great. But ...
That is the problem with Twitter Bootstrap, you have to change the
markup to fit to the CSS. And that is plain wrong. There are solutions
that help with responsive and grid layouts like Neat
(http://neat.bourbon.io/) where the CSS is generated for the markup
(the right way around).

@Samuel: What parts of Bootstrap do you use? Is this the new V3?

Thomas.

 
 
 Le 11/02/2014 15:42, Stephan Beal a écrit :
 Hi, all,

 i'm looking to clone someone's interesting fossil skin to snazz up my
 fossil repos a bit. Can any suggest a fossil repo with a nice skin?

 -- 
 - stephan beal
 http://wanderinghorse.net/home/stephan/
 http://gplus.to/sgbeal
 Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
 those who insist on a perfect world, freedom will have to do. -- Bigby Wolf

 
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
 
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users