Re: [fossil-users] Fossil 2.1 upgrade path

Got it. Thank you again and have a nice day! With best regards, Orzech Dnia 12 marca 2017 19:54 Richard Hipp d...@sqlite.org napisał(a): It will be inferred the first time you push a new SHA3 commit.___ fossil-users mailing list

Re: [fossil-users] Fossil 2.1 upgrade path

(a): On 3/12/17, Piotr Orzechowski fossi...@orzechowski.tech wrote: So active checkout must have this setting set, but clones created with Fossil 2.1 will use SHA-3 by default? No. If you create a new repository with 2.1, then it will use SHA3 by default. But existing repos will continue to use

Re: [fossil-users] Fossil 2.1 upgrade path

Thank you very much! So active checkout must have this setting set, but clones created with Fossil 2.1 will use SHA-3 by default? With best regards, Piotr Dnia 12 marca 2017 18:50 Richard Hipp d...@sqlite.org napisał(a): On 3/12/17, Piotr Orzechowski fossi...@orzechowski.tech wrote: Can I jump

[fossil-users] Fossil 2.1 upgrade path

Hello, thank you very much for this release. I have few self-hosted repositories that only I contribute to. What is my upgrade path? Can I jump directly from 1.37 to 2.1? Do I have to rebuild repositories, should I or maybe could I with some benefits? With best regards, Orzech

Re: [fossil-users] Conversation with a CM guy

And so does IntelliJ: https://www.jetbrains.com/help/idea/2016.1/merging-deleting-and-comparing-branches.html#d1537633e130. Regards, Orzech Dnia 17 maja 2016 21:01 Warren Young w...@etr-usa.com napisał(a): On May 17, 2016, at 12:25 PM, Ron W ronw.m...@gmail.com wrote: So far, none of the IDEs

Re: [fossil-users] Unrecognized command-line option, or missing argument: --https

Hi Warren, thanks for your help! In fact, I have already set an "A+" graded site. The problem is I'm hosting multiple repositories, as you can see here: https://orzechowski.tech. You solution seems to work with single repo only. I was just trying to migrate from xinetd to systemd with my fossil

Re: [fossil-users] Unrecognized command-line option, or missing argument: --https

Ah, I didn't read the: "At this stage, the standalone server (e.g. "fossil server") does not support SSL." here: https://www.fossil-scm.org/xfer/doc/trunk/www/server.wiki. Still, online help should mention that as well, IMHO. Regards, Orzech Dnia 11 maja 2016 21:08 Piot

Re: [fossil-users] Is fossil export known to be broken?

I've just looked at release notes for 1.34 and 1.33 and there was no straightforward note about need to rebuild repositories. Maybe it would be better to add such information to requiring release notes, or maybe even fossil would be able to suggest repo rebuilding itself? Pozdrawiam / With best

Re: [fossil-users] Is fossil export known to be broken?

ter to add to help that it is a good practice to run this command after each update. But then, why wouldn't rebuild happen automatically? Pozdrawiam / With best regards, Orzech W dniu 13.12.2015 o 18:00, jungle Boogie pisze: > On 13 December 2015 at 05:12, Piotr Orzechowski <orz...@drzewo.org

Re: [fossil-users] Is fossil export known to be broken?

Thanks for clarifying that. So I guess it would be either release note advise or schema change notification when running maybe even any command, if it was up to me. ;) Pozdrawiam / With best regards, Orzech W dniu 13.12.2015 o 22:58, Joerg Sonnenberger pisze: > I wouldn't advise to run it after

Re: [fossil-users] Can't build Fossil 1.34 with Tcl 8.5

Trying "make distclean" did not help, the error persisted. #define Tcl_Canceled(a,b) TCL_OK did its job well. :) Thanks, Joe! Pozdrawiam / With best regards, Orzech W dniu 03.11.2015 o 04:34, Joe Mistachkin pisze: > Did you try "make distclean" first? > I wrote both the Tcl and Fossil code in

Re: [fossil-users] Can't build Fossil 1.34 with Tcl 8.5

That #define looks scary, to be honest. ;) Pozdrawiam / With best regards, Orzech W dniu 02.11.2015 o 23:52, Joe Mistachkin pisze: > Piotr Orzechowski wrote: >> /fossil-src-1.34/./src/th_tcl.c:1069: undefined >> reference to `Tcl_Canceled' >> collect2: error: ld returned

[fossil-users] Can't build Fossil 1.34 with Tcl 8.5

Hi, I can't build Fossil 1.34 with Tcl 8.5 (8.5.0-2.1) on fully up-to-date Debian Wheezy 64-bit. I configure Fossil with: ./configure --prefix=/opt --with-openssl --with-tcl=/usr/lib/tcl8.5 --with-th1-hooks --json --with-zlib And I then get the following from make:

Re: [fossil-users] Two trunks?

W dniu 07.04.2015 o 18:03, Ron W pisze: I don't think they should be blocked, but the upstream repo should detect them and warn about them. If they can happen when two people push to central repository one after another, then IMHO they should be blocked. Or at least there should be a possibility

Re: [fossil-users] Two trunks?

Now I get it. Thanks for summing up your stance. Pozdrawiam / With best regards, Orzech W dniu 07.04.2015 o 20:17, Ron W pisze: I am saying warn. The louder the better. Naturally, when (a) auto-sync is enabled, and (b) you have connectivity with your upstream, then it is POSSIBLE for the

[fossil-users] Fossil with Tcl support does not work with nginx/xinetd

Hi, I have a Fossil setup running on Debian 7.8 64-bit inside OpenVZ container. I use nginx and xinetd to host my repositories. When I build Fossil from source without Tcl support - everything works fine. But when I build Fossil --with-tcl (Tcl 8.5), I can't display any repository through

Re: [fossil-users] Fossil with Tcl support does not work with nginx/xinetd

It looks like it's problem with xinetd. Do you know how to expose shared library to Fossil maybe? LD_LIBRARY_PATH is empty on Debian, and setting it through env in xinetd does not help. -- Pozdrawiam / With best regards, Orzech signature.asc Description: OpenPGP digital signature

Re: [fossil-users] Fossil with Tcl support does not work with nginx/xinetd

Finally I got it! I had to add env += FOSSIL_HOME=path to writable dir containing .fossil settings file line to /etc/xinetd.d/fossil configuration file. Thanks for your help! Pozdrawiam / With best regards, Orzech signature.asc Description: OpenPGP digital signature