Re: [fossil-users] Fossil 2.1 upgrade path

[Piotr Orzechowski]

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
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fossil 2.1 upgrade path

[Piotr Orzechowski]

What should I do to make my existing repositories default to SHA-3?
Should I set this hash-policy to sha3 on my server-side repositories too
or maybe it will be inferred default after first SHA-3 commit pushed to them?
Regards,
Orzech
Dnia 12 marca 2017 19:22 Richard Hipp d...@sqlite.org napisał(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 only SHA1 until you
request otherwise.
___
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 2.1 upgrade path

[Piotr Orzechowski]

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 directly from 1.37 to 2.1?
Yes. Simply download and install 2.1 and you are done.
Optional seconds step: Type "fossil hash-policy sha3" in a check-out
directory of any repository that you want to start using SHA3 hashes.
Then next time you do a commit from that check-out, the repo will will
automatically start doing all new commits as SHA3. If you do not care
aboud SHA1 vs SHA3, then you can safely ignore the second step.
___
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 2.1 upgrade path

[Piotr Orzechowski]

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
___
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] Conversation with a CM guy

[Piotr Orzechowski]

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 I've used seem to support VCS merges from within 
the IDE.
Visual Studio does, with Git:
 https://www.visualstudio.com/en-us/get-started/code/merging-with-squash
___
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

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

[Piotr Orzechowski]

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 configuration, 
but to no avail.
Regards,
Orzech___
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] Unrecognized command-line option, or missing argument: --https

[Piotr Orzechowski]

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 Piotr Orzechowski <fossi...@orzechowski.tech> 
napisał(a):

> Hello,
> 
> when I try to run fossil server behind https proxy with:
> 
> HOME=//fossil //fossil server --https --localhost --port  
> //fossil/
> 
> I get the following error:
> 
> unrecognized command-line option, or missing argument: --https
> 
> Am I doing something wrong? --https is listed as valid "server" option here: 
> https://www.fossil-scm.org/index.html/help?cmd=server.
> 
> Regards,
> Orzech
> 
___
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] Is fossil export known to be broken?

[Piotr Orzechowski]

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 regards,
Orzech

W dniu 13.12.2015 o 12:23, org.fossil-scm.fossil-us...@io7m.com pisze:
> On 2015-12-12T16:06:20 -0800
> jungle Boogie  wrote:
>> Great news!
>>
>> Did you happen to change your git version at all during either test?
> Nope, same version all along (2.6.2).
>
> M
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




signature.asc
Description: OpenPGP digital signature
___
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] Is fossil export known to be broken?

[Piotr Orzechowski]

I guess it would be better to change help message about rebuild then.
As of now, it says "Run this command after updating the fossil
executable in a way that changes the database schema." So I would
expect to see some information about such need in release notes.
Perhaps it would be better 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> wrote:
>> I've just looked at release notes for 1.34 and 1.33 and there was no
>> straightforward note about need to rebuild repositories.
>
> Admittedly I don't do it every time, but I thought that was something
> to be done for every update?
>
>
> Here's openBSD's port advising it's a good idea to run rebuild:
> http://openports.se/devel/fossil
>
> After upgrading to a newer version of fossil, it is always a good idea
> to run: "fossil all rebuild". Running "rebuild" this way is not always
> necessary, but it never hurts.
>
>
>




signature.asc
Description: OpenPGP digital signature
___
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] Is fossil export known to be broken?

[Piotr Orzechowski]

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 every update, especially for large
> repos. On something like NetBSD's src.fossil, it can take hours even on
> a fast machine.
>
> Joerg
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




signature.asc
Description: OpenPGP digital signature
___
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] Can't build Fossil 1.34 with Tcl 8.5

[Piotr Orzechowski]

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 question and I can personally assure
> you that it is safe (also I just tried it myself).  Simply run "./configure"
> with the desired arguments and then add the necessary line to "autoconfig.h"
> before running "make".  You may need to run "make distclean" first if there
> are compiled files from a previous attempt around.
>
> --
> Joe Mistachkin
>




signature.asc
Description: OpenPGP digital signature
___
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] Can't build Fossil 1.34 with Tcl 8.5

[Piotr Orzechowski]

Thanks, guys.

Adding --with-tcl-stubs and --with-tcl-private-stubs did not help.
I still get the:

bld/th_tcl.o: In function `evaluateTclWithEvents':
/fossil-src-1.34/./src/th_tcl.c:1069: undefined
reference to `Tcl_Canceled'
collect2: error: ld returned 1 exit status
make: *** [fossil] Błąd 1

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 1 exit status
>> make: *** [fossil] Error 1
>>
> Thanks for the report.  There are a couple workarounds:
>
>   1. use "--with-tcl-private-stubs=1" with configure.
>   2. #define Tcl_Canceled(a,b)  TCL_OK
>
> --
> Joe Mistachkin
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
W dniu 02.11.2015 o 23:50, Jan Nijtmans pisze:
> 2015-11-02 23:43 GMT+01:00 Piotr Orzechowski <orz...@drzewo.org>:
>> 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
> Just add the options --with-tcl-stubs and --with-tcl-private-stubs,
> then it will work fine. (Don't ask me why this isn't the default
> when using --with-tcl, I think it should be)
>
> Regards,
>  Jan Nijtmans
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users



signature.asc
Description: OpenPGP digital signature
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

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

[Piotr Orzechowski]

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:

/fossil-src-1.34/./src/th_tcl.c:1069: undefined
reference to `Tcl_Canceled'
collect2: error: ld returned 1 exit status
make: *** [fossil] Error 1

There was no such problem with Fossil 1.33 and there was no such problem
on Debian 8 Jessie with Tcl 8.6.

-- 

Pozdrawiam / With best regards,
Orzech




signature.asc
Description: OpenPGP digital signature
___
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] Two trunks?

[Piotr Orzechowski]

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 to enable/disable some kind of lock mechanism.

W dniu 07.04.2015 o 21:20, Ron W pisze:
 But the best way to avoid forks is good communication between
 contributors.
I agree that good communication is essential, yet I also think the best
way is to make software actively protecting us from making forks by
accident. E.g. block accidental forks on the same branch, but inform
user, that there's a possibility to --force push. I'm talking about
the git-like situation mentioned earlier.

Just my $0.02. ;)

-- 

Pozdrawiam / With best regards,
Orzech




signature.asc
Description: OpenPGP digital signature
___
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] Two trunks?

[Piotr Orzechowski]

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 commit to
 be blocked before the fork is committed. BUT, even then, there is
 still a window of vulnerability for 2 (or more) commits to the same
 parent.

 These accidental forks can and should be detected and warnings
 issued. The louder the better. Everyone committing to the project
 should see the warning. This way, it is less likely to accidentally
 loose an orphaned commit.

 Also, an upstream automatically blocking an incoming commit is
 anathema to Fossil's underlying promise to preserve the history. While
 Fossil does have a shunning mechanism, it is driven by explicit human
 intervention. This was designed that way because shunning discards
 information.

 Far better to auto-add a special tag (via the existing mechanism for
 adding tags to a commit) and have BOTH warnings displayed when the tag
 is received and timeline provide special highlighting of commits with
 the special tag.



signature.asc
Description: OpenPGP digital signature
___
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 with Tcl support does not work with nginx/xinetd

[Piotr Orzechowski]

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 browser.

I couldn't find any other info than nginx complaining about wrong HTTP
headers returning from upstream and then about connection reset by
upstream (upstream in nginx's terminology is a cluster that nginx can
proxy requests to). I build Fossil on my local Debian 7.8 64-bit
Virtualbox image and then put it on VPS with the same OS version. Both
have required libraries installed.

The Fossil binary itself seems to be working on-site when used in
command line mode. Fossil open, version and help do what they're
supposed to do. Also running fossil server on Virtualbox seems to work
fine, as I can browse repository through it's web interface. Only xinetd
+ nginx seem to be not working for some reason (on both Virtualbox image
and VPS) unless I switch to Fossil binary compiled without Tcl support.

The flag I used to compile Fossil was --with-th1-hooks and
--with-tcl=path_to_tclConfig.sh. Also there's HTTPS and readline
support built-in.

So the question is, does Tcl support require some special steps or
environment setup to work? Is there any other thing I should check or
look at?

Thanks in advance!

-- 

Pozdrawiam / With best regards,
Orzech




signature.asc
Description: OpenPGP digital signature
___
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 with Tcl support does not work with nginx/xinetd

[Piotr Orzechowski]

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
___
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 with Tcl support does not work with nginx/xinetd

[Piotr Orzechowski]

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
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users