Re: [fossil-users] cannot connect to host

Is anyone else having trouble syncing with Chiselapp lately? None of my Chiselapp local repos can sync, whereas my non-Chiselapp (lua.sqlite.org) repo is syncing fine. [Note that I did `fossil configuration push all` on only one of my local repos, so this isn't the cause of my problem, as I

Re: [fossil-users] cannot connect to host

I can sync with chiselapp using http. My fossil is built without ssl so I can't try https. 2015-08-31 18:08 GMT+02:00 Doug Currie : > Is anyone else having trouble syncing with Chiselapp lately? None of my > Chiselapp local repos can sync, whereas my non-Chiselapp

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Aug 30, 2015, at 2:27 AM, Stephan Beal wrote: > > On Sun, Aug 30, 2015 at 10:15 AM, Baptiste Daroussin > wrote: > > Number #1 is the inhability to run "external" hooks easily > > it's difficult to do portably system() is ANSI C. There

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Mon, Aug 31, 2015 at 6:40 PM, Warren Young wrote: > On Aug 30, 2015, at 2:27 AM, Stephan Beal wrote: > > it opens up many more potential failure cases > > I don’t see what’s difficult about failing a transaction if a hook is > defined and the external

Re: [fossil-users] cannot connect to host

Thanks, Goyo. My problem seems to be SSL >> SSL: cannot connect to host chiselapp.com:443 () e On Mon, Aug 31, 2015 at 12:17 PM, Goyo wrote: > I can sync with chiselapp using http. My fossil is built without ssl > so I can't try https. > > 2015-08-31 18:08 GMT+02:00 Doug

Re: [fossil-users] cannot connect to host

Hi Doug, On 31 August 2015 at 09:08, Doug Currie wrote: > Is anyone else having trouble syncing with Chiselapp lately? None of my > Chiselapp local repos can sync, whereas my non-Chiselapp (lua.sqlite.org) > repo is syncing fine. [Note that I did `fossil configuration push

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

There are docs on --with-tcl and the commands it provides (see th1.md in the source tree). Also, with Tcl enabled the hooks work perfectly for sending mail and I've personally been doing so for several years on a repository of mine. Sent from my iPhone > On Aug 31, 2015, at 9:40 AM, Warren

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Aug 31, 2015, at 10:46 AM, Stephan Beal wrote: > > The push fails because a remote hook disallows it. What then? The same thing that happens when you try to push to a read-only repo, or push while the Internet connection is down, or push to a repo you accidentally

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Aug 31, 2015, at 10:59 AM, Joe Mistachkin wrote: > > > There are docs on --with-tcl and the commands it provides (see th1.md in the > source tree). Yes, I already saw that, via the web: http://fossil-scm.org/index.html/doc/tip/www/th1.md You have to admit, it’s

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Mon, Aug 31, 2015 at 7:27 PM, Warren Young wrote: > > That becomes fossil's problem > > No, it’s the hook-writer’s problem. > > The hook-writer solves that in the normal way: log the problem so that a > human can figure out how to solve it, then retry the commit. > Hooks

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Aug 31, 2015, at 11:39 AM, Stephan Beal wrote: > > Hooks are not just about emails, but about policy decisions. "Does this file > conform to XYZ." A failure at that level is unrecoverable without changing > the policy. I think we can agree that using hooks to

[fossil-users] Modifying button bar

I am new to using Fossil, so I created a dummy project to play with the various features. For the most part I think Fossil is a huge improvement over the alternatives. I can see using this as my support website framework along with handling development issues., which leads me to the

Re: [fossil-users] Modifying button bar

On Aug 31, 2015, at 11:46 AM, Scott Doctor wrote: > > how can I customize the buttons on the button bar at the top of the page Admin -> Skins -> Header. That gets you a text editor containing the current HTML + TH1 code combination that generates the header portion of

Re: [fossil-users] cannot connect to host

On Mon, Aug 31, 2015 at 12:58 PM, jungle Boogie wrote: > I can clone, over TLS, one of the many public repos, but I don't have > access to any of them to sync. > > So, I just tried cloning using https to no avail: test e$ fossil clone

Re: [fossil-users] Modifying button bar

Hmm. I guess that will work. but would be nice to have a simple GUI-ish type editor where I just have a list in order of appearance that is the name of the button and its link, instead of basically hacking code, thereby isolating language syntax from the

Re: [fossil-users] Modifying button bar

On 8/31/15, Scott Doctor wrote: > > Hmm. I guess that will work. but would be nice to have a simple GUI-ish type > editor where I just have a list in order of appearance that is the name of > the button and its link, instead of basically hacking code, thereby > isolating

Re: [fossil-users] cannot connect to host

On 31 August 2015 at 10:51, Doug Currie wrote: > test e$ fossil clone https://chiselapp.com/user/e/repository/ldecNumber > ldecNumber.fossil > SSL: cannot connect to host chiselapp.com:443 () > Clone done, sent: 0 received: 0 ip: > server returned an error - clone aborted

Re: [fossil-users] Markdown checkin comments and tickets (was: Multi line formatting)

On Mon, Aug 31, 2015 at 1:56 PM, Warren Young wrote: > On Aug 31, 2015, at 11:46 AM, Warren Young wrote: > > I think we can agree that using hooks to enforce, say, code formatting > rules is a bad idea. > > I did a bit of Googling, and this blog article

Re: [fossil-users] cannot connect to host

On Mon, Aug 31, 2015 at 2:21 PM, jungle Boogie wrote: > On 31 August 2015 at 10:51, Doug Currie wrote: > > test e$ fossil clone https://chiselapp.com/user/e/repository/ldecNumber > > ldecNumber.fossil > > SSL: cannot connect to host

Re: [fossil-users] Modifying button bar

On Mon, Aug 31, 2015 at 1:51 PM, Warren Young wrote: > On Aug 31, 2015, at 11:46 AM, Scott Doctor wrote: > > > > how can I customize the buttons on the button bar at the top of the page > > Admin -> Skins -> Header. Or just: Admin -> Header (At least

Re: [fossil-users] cannot connect to host

Hi Doug, On 31 August 2015 at 12:18, Doug Currie wrote: > > > On Mon, Aug 31, 2015 at 2:21 PM, jungle Boogie > wrote: >> >> On 31 August 2015 at 10:51, Doug Currie wrote: >> > test e$ fossil clone

Re: [fossil-users] cannot connect to host

On Mon, Aug 31, 2015 at 3:32 PM, jungle Boogie wrote: > % fossil version -v > This is fossil version 1.33 [7febc31883] 2015-08-29 15:24:16 UTC > Compiled on Aug 29 2015 16:15:07 using gcc-4.2.1 Compatible FreeBSD > Clang 3.4.1 (tags/RELEASE_34/dot1-final 208032) (64-bit)

Re: [fossil-users] cannot connect to host

On Aug 31, 2015, at 1:58 PM, Doug Currie wrote: > > SSL (LibreSSL 2.2.2) > ... > Seems to work fine for me! [snip] > I'm still stuck: > ... > SSL (OpenSSL 0.9.8zg 14 July 2015) Is the difference in the SSL libraries? Although you’re using the latest OpenSSL 0.9.8, that

Re: [fossil-users] cannot connect to host

On 31 August 2015 at 13:32, Warren Young wrote: > On Aug 31, 2015, at 1:58 PM, Doug Currie wrote: >> >> SSL (LibreSSL 2.2.2) >> ... >> Seems to work fine for me! > > [snip] > >> I'm still stuck: >> ... >> SSL (OpenSSL 0.9.8zg 14 July 2015) > > Is the

Re: [fossil-users] cannot connect to host

On Aug 31, 2015, at 2:36 PM, jungle Boogie wrote: > > SSL (OpenSSL 1.0.1p-freebsd 9 Jul 2015) OpenSSL 1.0.1 is still considerably advanced beyond 0.9.8. According to this analysis, they broke over a quarter of the ABIs when moving from 0.9.8 to 1.0.0, and another 5%

Re: [fossil-users] cannot connect to host

On Aug 31, 2015, at 2:56 PM, Warren Young wrote: > > On Aug 31, 2015, at 2:36 PM, jungle Boogie wrote: >> >> SSL (OpenSSL 1.0.1p-freebsd 9 Jul 2015) > > OpenSSL 1.0.1 is still considerably advanced beyond 0.9.8. > > According to this analysis, they

Re: [fossil-users] cannot connect to host

On Mon, Aug 31, 2015 at 5:07 PM, Warren Young wrote: > My guess: The SSL implementation running on ChiselApp has been tightened > down, to make it refuse old broken SSL features that used to work in the > past, as a result of all the security problems found in OpenSSL over the

Re: [fossil-users] cannot connect to host

On Aug 31, 2015, at 3:27 PM, Doug Currie wrote: > > On Mon, Aug 31, 2015 at 5:07 PM, Warren Young wrote: > My guess: The SSL implementation running on ChiselApp has been tightened > down, to make it refuse old broken SSL features that used to work in