[fossil-users] Latest stable release or dev release does not compile with option: --static

Hello, Latest stable release or dev release does not compile with option: --static This issue occur with/without openSSL. I would like to point you out that readline is not used. Distribution : Porteus 1.2, 64bit. (Slackware based live CD) Latest stable release or dev release does not compile

Re: [fossil-users] Latest stable release or dev release does not compile with option: --static

-DLL = Windows. I do not use window$ -Warning does not stop compiling... :-) -Why do I ask for --static compilation to succeed Don't forget that if you would like Fossil to be used, it must be easy to compile, especially with option --static. People would like to use a DVCS everywhere with any

Re: [fossil-users] Latest stable release or dev release does not compile with option: --static

Hello everyone, Can't we use GnuTLS instead of openSSL ? Wget decided to use GnuTLS instead of openSSL... Best Regards K. D. Richard Hipp wrote: K. Fossil user  wrote: People would like to use a DVCS everywhere with any distro with the SAME binary, not the one specific to a distro. I

Re: [fossil-users] Latest stable release or dev release does not compile with option: --static

Hello all of you,   1/ Jan Nijtmans wrote: I agree with others' remarks, that --static doesn't make sense on modern systems any more. I do not agree with such statement. Static is important because mostly we do use two or more systems. (debian and centos for example) Darcs is static and runs

Re: [fossil-users] Latest stable release or dev release does not compile with option: --static

Hello, copy error in my last mail: correct copy is below : $ ./configure --prefix=/usr --sysconfdir=/etc \ --with-openssl=auto \ --json \ --markdown $ make ## ... HTTPS support enabled Checking for readline/readline.h...not found Checking for editline/readline.h...not found Checking libs for

Re: [fossil-users] Latest stable release or dev release does not compile with option: --static

$ fossil update ba86c859df checkout: ba86c859dff83e89640091ea18dec5571630af2a 2013-01-31 18:12:54 UTC tags: trunk comment:  Added an extern to work around a duplicate-definition linking   error with the tcc compiler. (user: stephan) changes:  None. Already

Re: [fossil-users] Latest stable release or dev release does not compile with option: --static

1/ GLibc and linux symbols versionning issue then... OK, thanks. 2/ runs everywhere: I mean, it should run in every plateform... but not cross platform of course. It is not about java bytecode thing... :D For example, if someone do fossil compilation with i386, then ALL i386 linux should be

Re: [fossil-users] Latest stable release or dev release does not compile with option: --static

So you have to build an executable per-distro -- welcome to Linux. Is it the same with *BSD systems ? (Thank you for your tought: it's really appreciated !)   Best Regards K. Nico Williams wrote: bld/shell.o: In function `find_home_dir': ./src/shell.c:2739: warning: Using 'getpwuid' in

Re: [fossil-users] I suggest a lite release of fossil so --static could be used

1/ RedHat is a company that needs to earn money. If static compiling is used then few people may need to buy their products. If you read what is written, it is not said IMPOSSIBLE. It is said DISCOURAGED, which is TOTALLY not the same. As I said, it should be possible to dynamically linking, but I

Re: [fossil-users] I suggest a lite release of fossil so --static could be used

You do understand what Stephan said. It is not what I've said, it is what Stephan said... I agree with you. I do not use network either... However, my discuss is more about the fact that people do care about the way how they may use it without dependencies... Less dependencies means less

Re: [fossil-users] Latest stable release or dev release does not compile with option: --static

On 1/31/2013 12:35 PM, K. Fossil user wrote: Hello all of you, Hello. 2/ serious issue I've downloaded today's timeline trunk: $ ./configure --prefix=/usr --sysconfdir=/etc \ --with-openssl=none \ --static \ --json \ --markdown $ make ## all seems ok ! $ sudo make install $ fossil open

[fossil-users] 101 entries... when it should be 200...

Hello again, Click on Timeline then click on tags: trunk finally click on button 200 entries I can read 101 entries... when it should be 200... Two buttons appear [20 entries], which is correct and [200 entries] that should not exists... date in the bottom is 2013-01-03 22:33   Best Regards

Re: [fossil-users] 101 entries... when it should be 200...

, change it to :   else if( nEntry200 ){   Best Regards K. Stephan Beal wrote : On Fri, Feb 8, 2013 at 2:44 PM, K. Fossil user wrote: I can read 101 entries... when it should be 200... Two buttons appear [20 entries], which is correct and [200 entries] that should not exists... Does your

Re: [fossil-users] 101 entries... when it should be 200...

 : Stephan Beal sgb...@googlemail.com À : Fossil SCM user's discussion fossil-users@lists.fossil-scm.org Envoyé le : Vendredi 8 février 2013 14h25 Objet : Re: [fossil-users] 101 entries... when it should be 200... On Fri, Feb 8, 2013 at 3:14 PM, K. Fossil user ticketpersonnal-fos...@yahoo.fr wrote

Re: [fossil-users] 101 entries... when it should be 200...

AM, K. Fossil user ticketpersonnal-fos...@yahoo.fr wrote: Hello again, Click on Timeline then click on tags: trunk finally click on button 200 entries That button really means at most 200 entries but that is too much text for a button, so it is abbreviated to just 200 entries.   I can read

Re: [fossil-users] 101 entries... when it should be 200...

1/ I agree with the 20-200, but my idea is this : I would like to know which button I've pressed: 200 or 20 ? (it doesn't matter if n=100) Never mind, this is not that important for me. It could be that important for some people... 2/ The timeline variant is strange, because I've thought that if

[fossil-users] I do want open --keep to be possible with updates

Hello, fossil open myrepo.fossil --keep fossil update  ## updates downloads files and they are stored in the current directory. Can't fossil do something like : fossil update --keep # so NO files are written in the current directory ?   Best Regards K.

Re: [fossil-users] I do want open --keep to be possible with updates [solved]

, February 21, 2013, K. Fossil user wrote: Hello, fossil open myrepo.fossil --keep fossil update  ## updates downloads files and they are stored in the current directory. Can't fossil do something like : fossil update --keep # so NO files are written in the current directory ?   Best Regards

[fossil-users] Should mail be seen or not ?

It is strange to me to see my mail in your mailing list response.Is it not supposed to be hidden ? Even for respect to people privacy ? I'm asking because suppose that I don't want to be spammed because of this, it would be hard to stop spams, even with appropriate tools...   Best Regards

[fossil-users] some e-mails goes to the spam box

Hi, It seems that some mails goes to the spam box... I've noticed this when it comes to David Simmons e-mail. Did someone have this issue ? Could it be fixed ?   Best Regards K. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org

Re: [fossil-users] Fossil :: typos

Hi, People read docs : this is one way to find typos... :-)just sayin'  Best Regards K. De : Richard Hipp À : Fossil SCM user's discussion Envoyé le : Mardi 21 juin 2016 20h04 Objet : Re: [fossil-users] Fossil :: typos On

Re: [fossil-users] Further mailing list configuration changes.

I don't understand why the Fossil team don't create a poll about the Mailing list behavior people may want ?Is it so hard to do ? The main reason i've read, that people said, was : "Dear Fossil, we could not filter so don't change the first behavior".My filters run correctly why not the others

[fossil-users] Your membership in the fossil-users mailing list is currently disabled due to excessive bounces

Hello again, I've received that message :"Your membership in the fossil-users mailing list is currently disabled due to excessive bounces" That's not serious ... ><  Best Regards K.___ fossil-users mailing list fossil-users@lists.fossil-scm.org

Re: [fossil-users] Further mailing list configuration changes.

e poll... How could I convince people to use Fossil if even a poll is an issue,or worst irrelevant ? Best Regards K. De : Andy Bradford <amb-sendok-1469675137.ehjibpjdkmnieipof...@bradfords.org> Cc : Fossil SCM user's discussion <fossil-users@lists.fossil-scm.org> Thus said

Re: [fossil-users] Further mailing list configuration changes.

I would test 1.35, because I like it, but at this level of discuss I don't think that I would give any information about bugs I would found : it's a lose of time I don't want to deal with.I guess that someone will found them... Thank you for reading. Best Regards K. De : Andy Brad

Re: [fossil-users] Linux binary downloads

> « 1.37.1 » ??? AH ?We were told that this would never occur [inside the Fossil Realm].Even a non official binary should not use that numbering because it is disrespectful. Surprisingly you've decided to do whatever I've said :a) Use little numbering for little fixesb) Use latest SQLite when

Re: [fossil-users] Google Security Blog: Announcing the first SHA1 collision

1/ Warren the guy who knows nothing about software security talks about software security ...Wow. I don't get this. 2/ semi? > « I think Fossil is in a much better position to do this sort of migration > than, say, Git, due to its semi-centralized nature » This would convince people to use

Re: [fossil-users] Google Security Blog: Announcing the first SHA1 collision

Thank you Marc... 1/ I've said that it is needed to let people choose their digest algorithm... a) of course the Fossil team does not take into account what I've said. b) I was wondering in the past when would it be possible to the lambda guy to break the sha1.Finally it is worse than what I've

Re: [fossil-users] Google Security Blog: Announcing the first SHA1 collision

Hello, Does this mean that it is not so hard to adapt SHA algorithm to a better one ?:D DRH suspected that it would be hard :D :D :D Of course I don't agree with DRH ; I will never agree with him about security discuss either ... :-| Thank to "sgbeal". :-)   Best Regards K. De : Stephan

Re: [fossil-users] Google Security Blog: Announcing the first SHA1 collision

Hello, I can't believe that a so called community manager (Warren) could say theses ...  :D I assume that most of you have read Warren Stuff ? 1/ Hey Warren, you know nothing about security software so don't speak about it. :-| 2/ CentOS does not need any advice from you : they know their

Re: [fossil-users] Why we should NEVER use inetd/xinetd

man ! :-D Best Regards K. De : Luca Ferrari <fluca1...@infinito.it> À : Fossil SCM user's discussion <fossil-users@lists.fossil-scm.org> Envoyé le : Mercredi 26 octobre 2016 6h25 Objet : Re: [fossil-users] Why we should NEVER use inetd/xinetd On Wed, Oct 26, 2016 at 1:0

[fossil-users] Which IDE is good with Fossil ?

Hi, I would like to have some information, even little one about IDE that have Fossil as a DVCS (even a plugin that is experimental). a) glade/GTK based IDE    Qt based     wxWidget based    Python based    Java based     etc. b) it could be interesting if you could give your point of view about

Re: [fossil-users] OT: Why we should NEVER use inetd/xinetd

Hi, >« The security concerns come in as a result of not paying attention to the >details of the implementation » Oh I forgot this. In the past, it was my tought. But as the expert explain to us, it is not only implementation. Theses days, we all hear about DDOS that could not be stopped, not

Re: [fossil-users] Why we should NEVER use inetd/xinetd

Hi, >« Oh, I thought we were on fossil-users here... » Many people are interested in security talks, but not you. You are so good in this area, aren't you ? When it comes to servers, especially TCP/IP things, one should consider security seriously. People will talk again to you the day when a

Re: [fossil-users] sites inaccessible

Hi, Yesterday I've noticed that Fossil was down for a long time...drh said one day that inetd stopped : may be it was the case yesterday ?   Best Regards K. De : jungle Boogie À : General Discussion of SQLite Database ;

Re: [fossil-users] OT: Facebook engineers preferring hg to Git

Hi, Below are answered I give to few people (Richard, etc.) who talk about this topic. > « Irony: Isn't Rust heavily dependent upon Git for its package management? So > if Hg is written in Rust, does that mean that Hg has a dependency on Git? » Rust is a language, Git is a DVCS. You can use

Re: [fossil-users] Follow-up to reverting missing files

Hi, 1/ I've got a question : is bogus bounces NOT already solved ? 2/>backticks instead [of $(...)] Can't we use pipes ?   Best Regards K. De : Andy Goth À : Fossil Users Mailing List Envoyé le : Mercredi 9 novembre 2016

Re: [fossil-users] Download v1.36 Linux x86 tar.gz actually contains 64bit binary

Hi, Yes, you should not give something dynamic to people ...I guess that it is 64 bits because they are not aware by the fact that they should compile for both architectures (32 bits AND 64 bits binary)? I've recommended to the Fossil team that they should create a 1.36.1 release because most

Re: [fossil-users] on sha1 as a hash

Hi, In this thread I try to: give short answer to what I've read, then I give my opinion, and finally I put some suggests : 1/ Thanks to people who give their opinions and technical point of view in this topic.2/ I know that Git uses sha1, debian uses md5,sha1,sha256 , etc. ...The point is not

Re: [fossil-users] features I'd like to have in fossil

Hi, I don't have much time now but I just answer to what you've said : No I don't ask Fossil team to switch now over MatterMost.I ask them to think about it. I remind you that I am not the owner of the Fossil. It is not because I ask it for the Best of Fossil that it would mean that I do want

[fossil-users] Why we should NEVER use inetd/xinetd

Hi, I was wondering if it is necessary to create a new thread just for inetd/xinetd... Two guys said this : >« Wait, what's wrong with inetd? » and, this : >« That ellipsis really should be filled in with more details. Would you >perhaps be willing to elaborate a bit on what you mean? » These

Re: [fossil-users] features I'd like to have in fossil

Hi, >« This is "fossil-users" mailing list, and it exists to share opinions, problems, issues, suggestions and so on, would you agree to that? » Exactly my tought. >« learning curve » I've said something about that. >« The less people use it - the less new ideas, less improvements and

Re: [fossil-users] remote check in

Hi, >« So do people who have a check-in or a new file email the file to the administrator and they add/check-in, or do those people have command line access? » 1/ People don't really use Fossil : they do use git/mercurial/etc. 2/ Those who use Fossil use command line most of them. 3/ The purpose

Re: [fossil-users] disabled due to excessive bounces (again?)

h56 Objet : Re: [fossil-users] disabled due to excessive bounces (again?) On Oct 16, 2016 6:35 PM, "K. Fossil user" <ticketpersonnal-fos...@yahoo.fr> wrote: > > I am angry because Fossil knows nothing about marketing which is bad for any > project...If I may paraph

Re: [fossil-users] disabled due to excessive bounces (again?)

Hi again, 1/ Malware or anything related? NOT at all ! 2/ Yep resubscribe. However it could bother some people (not me tough). Best Regards K. De : Scott Doctor À : Fossil SCM user's discussion Envoyé le : Mardi 18 octobre

Re: [fossil-users] Why we should NEVER use inetd/xinetd

Hi, Thanks to Joerg who give some nice perspective about software. Thank to Warren which tries to talk. Warren said : >« I just did a search for inetd at the NVD CVE search, and got nothing >relevant to running Fossil under inetd » a) I don't talk about Fossil. My talk is about inetd/xinetd

Re: [fossil-users] features I'd like to have in fossil

Hi, >« Be concrete: how do you want tags to work which makes them entirely >different from branches? » I've said that tags and branches are the same technically speaking. However, for people those are not the same : for example the master branch is a special branch. When in git you do : git

Re: [fossil-users] Can fossil bind to a single address?

Hi, However, xinetd or inetd are not recommended... Best Regards K. De : Nathaniel Reindl À : fossil-users@lists.fossil-scm.org Envoyé le : Vendredi 21 octobre 2016 21h48 Objet : Re: [fossil-users] Can fossil bind to a single address? On Fri, Oct 21, 2016, at

Re: [fossil-users] features I'd like to have in fossil

Hi again, Most of the time I try not to interact with people discuss. However, I was astonished by what a community manager answered to another guy. So I decided to give my opinion about it. > « You admitted to not using branches, apparently because you don’t see the > point of them in a

Re: [fossil-users] on sha1 as a hash

Hi, 1/ Does Fossil use SHA1 ?OoToo bad if it is.At least I expect that we've got a choice : sha256, sha512, etc. ... 2/ However, when people use Fossil in a local PC, even MD5 should not be an issue.3/ Thanks for this reminder.   Best Regards K. De : bch À :

Re: [fossil-users] Download v1.36 Linux x86 tar.gz actually contains 64bit binary

On Sat, Nov 12, 2016 at 1:24 AM, K. Fossil user <ticketpersonnal-fos...@yahoo.fr> wrote: > Explain me why a SO serious project could not wait for 10 days or if it is > not that possible (I don't see why ??), why don't Fossil create a 1.36.1? Sorry pal, my guess is that the latest sql

Re: [fossil-users] Download v1.36 Linux x86 tar.gz actually contains 64bit binary

ts.fossil-scm.org> Envoyé le : Vendredi 11 novembre 2016 11h38 Objet : Re: [fossil-users] Download v1.36 Linux x86 tar.gz actually contains 64bit binary On Wed, Nov 9, 2016 at 4:16 PM, K. Fossil user <ticketpersonnal-fos...@yahoo.fr> wrote: > Beyond that, I don't understand why

Re: [fossil-users] Download v1.36 Linux x86 tar.gz actually contains 64bit binary

a simple thing for us :create a filter where "K. Fossil user" should be thrown in the dust-bin of your MUA. e1) You will avoid me to see your stuff e2) You will avoid people to read our stuffs... e3) You won't deserve anything from me so I will be glad if you do that ... PLEASE Mr Parsons (

Re: [fossil-users] Download v1.36 Linux x86 tar.gz actually contains 64bit binary

f view before yours)I believe I addressed > this above.> >   > Best Regards > > K. > > > > De : Luca Ferrari <fluca1...@infinito.it> > > À : Fossil SCM user's discussion <fossil-users@lists.fossil-scm.org> > Envoyé

Re: [fossil-users] Why we should NEVER use inetd/xinetd

d : 4. What Is A "Bikeshed"? NOT bikeshed.org. De : Luca Ferrari <fluca1...@infinito.it> À : Fossil SCM user's discussion <fossil-users@lists.fossil-scm.org> Envoyé le : Vendredi 28 octobre 2016 6h29 Objet : Re: [fossil-users] Why we should NEVER use inetd/xinetd

[fossil-users] Version 1.34 (2016-11-02) ?

Hi, Fossil: Download Page http://www.fossil-scm.org/index.html/uv/download.html « Version 1.34 (2016-11-02) » I was looking for the 1.34 release date when I do read this « Version 1.34 (2016-11-02) »... I didn't know that Fossil 1.34 is next week ... :-? I was told that next release should be

Re: [fossil-users] Error compiling FOSSIL trunk

Hi, I agree with Scott. The checkin should not change many things (nothing with VS) when it comes to compiling...(The latest release is not that far...) That's the point.   Best Regards K. De : Richard Hipp À : Fossil SCM user's discussion

Re: [fossil-users] Facebook engineers preferring hg to Git

Hi, You've got interesting points here. Like it ! :-) I've never heard that Rust must use Git.Of course if you do use cargo, you should think about a DVCS but that does not mean that you could not use Fossil or something else.Just play with your own IDE and this should suffice. IMHO people

Re: [fossil-users] Fossil on HN

I read this :"Please steal ideas and code from Fossil"There are no serious reason for people to use Fossil.In the past I was a huge fan of it... 1/ I ask for a poll I was told that I was ... (no matter what).2/ I've tried to compile Fossil it did not... In the past, it did nicely: I've created

Re: [fossil-users] www.fossil-scm.org down? security issue ?

Security issue ?Ah yes, security is not the first target for Fossil. I was told by a security computer specialist that we should NEVER use xinetd, xinitd or something related...Of course, for the Fossil team, people I do know are not good enough ... :-D (One day I was wondering if downloading

Re: [fossil-users] autosetup: hidden autoconf/automake compatibility

Hi, "They just add overhead to debugging build problems for no good reason" Not necessary an issue.Some people would like more verbosity, some others no verbosity.However, if you don't want those options, don't use them :-) In debian realms, those options are most of the time used and I agree

[fossil-users] disabled due to excessive bounces (again?)

Hi again, Ah I forgot something like this : "Your membership in the mailing list fossil-users has been disabled due to excessive bounces The last bounce received from you was dated 16-Oct-2016.  You will not get any more messages from this list until you re-enable your membership.  You will

Re: [fossil-users] autosetup: hidden autoconf/automake compatibility

Hi, The good question is : Why don't they use autoconf/automake like most people do, at least CMake even if I don't agree with this ? Snobism ? :-P (LOL)   Best Regards K. De : Osamu Aoki À : fossil-users@lists.fossil-scm.org Envoyé le : Samedi 15 octobre 2016

Re: [fossil-users] Fossil on HN

Hi, 1/ "it is a do-ocracy"We didn't know that. NOW I DO KNOW ! Thank you.I don't think that the owner of a project will give the keys to the average people, do you ?However, the leader of any project knows who to listen to. 2/  "I’ve rebuilt Fossil several times over the past few days.  It

Re: [fossil-users] disabled due to excessive bounces (again?)

ything but who knows... Best Regards K. De : Steven Gawroriski <ste...@multiphasicapps.net> À : fossil-users@lists.fossil-scm.org Envoyé le : Dimanche 16 octobre 2016 12h08 Objet : Re: [fossil-users] disabled due to excessive bounces (again?) On Sun, 16 Oct 2016 03:27:02 + (UTC) &qu

Re: [fossil-users] disabled due to excessive bounces (again?)

bounces (again?) On Sun, Oct 16, 2016 at 03:27:02AM +, K. Fossil user wrote: > Try to convince people to use Fossil after that : very hard. Can you please take your negative and hostile attitude somewhere else? It seems clear now that you have a number of problems on your side. >Fro

Re: [fossil-users] Bug report: Terrible Performance, when Checking in LLVM Source

Hi, @Martin Vahi said : > « [...] CPU is AMD 64bit [...] » I don't know what AMD 64 means for you : it could be a dual core or a Quad core, and who knows an optocore... The amount of RAM could let the calculation of the Checksum be faster ... The bus speed can help a lot etc. > « [...] The

Re: [fossil-users] Fossil 2.1

1/ Git is better than Fossil when it comes to the job to be done. period. 2/ nine days after first commit is not evidence of efficiency. a) it could be an evidence of issues. Windows compilation issue was reported after commits in the past.That kind of issue is totally abnormal. b) The version

Re: [fossil-users] Fossil 2.0 for win64 [Was: Fossil Version 2.0]

Is your Fossil app compiled with the Official SQLite ? As I remember, you seem to have a better approach ... [a better SQLite] Just sayin'   Best Regards K. De : Jan Nijtmans À : Fossil SCM user's discussion Envoyé le :

Re: [fossil-users] Fossil Version 2.1 (prerelease)

DRH question is strange in fact ... Not everyone would go for a Fossil 2.0 just because their repo ARE SHA1. Not to mention that, some providers won't move immediately when a stable release will come. I've said it in the past : a command line with option such as --sha1 --sha256 and so on is

Re: [fossil-users] Fossil 2.1 beta. Was: Progress report of Fossil 2.x

Ah ? really ? 1/ I am one of the guys who talks about security here. I am not the first one.SHA1 was one of the discuss... 2/ I am one of the first guy who give many examples of good way to use a specific hash algorithm... (when you use command line) If honesty occur here, kudos should go to us

Re: [fossil-users] warning about unsaved changes with `fossil checkout --keep`

Hi, It is better if you could give to people the release you do use... (1.37 ?) Some people do use a release that is inside some public servers which are not always up to date.Not to mention that most of the time the official (say stable) release is not the latest release which is less buggy ...