Re: [fossil-users] Small tweak to fix compilation issue (at least on Solaris 11)

2016-08-29 Thread Warren Young
On Aug 28, 2016, at 5:30 AM, Karel Gardas wrote: > > while building fossil-head just from minutes ago, my compiler on > Solaris 11.2 complain about: > > cc -I. -I../src/src -Ibld -D_XOPEN_SOURCE=500 -D__EXTENSIONS__ > -DFOSSIL_DYNAMIC_BUILD=1 -g -O2 -DHAVE_AUTOCONFIG_H >

Re: [fossil-users] Directory symlinks...

2016-09-30 Thread Warren Young
On Sep 30, 2016, at 4:37 PM, Joe Mistachkin wrote: > > Are having directory symlinks (on Unix) supposed to be supported? > If not, is anybody willing to help me add support for them? Well, that’s a tricky one, innit? Fossil manages files, not directories, but Fossil’s

Re: [fossil-users] Fossil on HN

2016-10-10 Thread Warren Young
On Oct 10, 2016, at 12:36 PM, Konstantin Khomoutov wrote: > > On Mon, 10 Oct 2016 14:49:55 -0300 > Richie Adler wrote: > > [...] >> Fossil is a perfect example of an excuse that has to die. *Nobody* >> has the excuse that version control

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

2016-10-27 Thread Warren Young
On Oct 27, 2016, at 5:37 AM, David Mason wrote: > > Also of interest is that Facebook is doing an implementation of hg in Rust. Facebook’s market cap is $343.34 billion today. This is relevant because... > Fossil seems pretty robust in C, but Rust would increase safety

Re: [fossil-users] rebuild scale-ability/data written/repo size ratio

2016-10-28 Thread Warren Young
On Oct 28, 2016, at 3:45 AM, Karel Gardas wrote: > > make it more scale-able and allow its real usage also for projects of > bigger size. How many projects are there bigger than SQLite, percentage-wise? Has anyone done something like produce a SLOC histogram for all projects

Re: [fossil-users] Directory symlinks...

2016-10-28 Thread Warren Young
On Oct 28, 2016, at 3:29 PM, Steven Gawroriski wrote: > > On Fri, 30 Sep 2016 21:25:01 -0700 > "Joe Mistachkin" wrote: > >> I've checked in a fix on the dirSymlinks branch that appears to >> completely fix the issue I personally encountered.

Re: [fossil-users] windows compiling with MS VC

2016-10-24 Thread Warren Young
On Oct 24, 2016, at 3:12 PM, jungle Boogie <jungleboog...@gmail.com> wrote: > > On 24 October 2016 at 13:08, Warren Young <w...@etr-usa.com> wrote: >> VS2015 x86 Native Tools Command Prompt. > > SUCCESS! I had put this big ugly thing in my path thinking it had

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

2016-10-21 Thread Warren Young
On Oct 21, 2016, at 10:02 AM, Nikita Borodikhin wrote: > > == color support - review the change, history analysis == > > One should not underestimate the significance of color on terminals these > days, that's why both git and mercurial and a lot of tools have color support

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

2016-10-21 Thread Warren Young
On Oct 21, 2016, at 5:57 PM, K. Fossil user wrote: > > However, I was astonished by what a community manager answered to another guy. You say that like you think I hold some kind of official title. I’m just another Fossil user, like you. When I used that

[fossil-users] How git does "fossil up 2016-08-01"

2016-10-21 Thread Warren Young
I just had to share this blog post, which I found last night: http://blog.endpoint.com/2014/05/git-checkout-at-specific-date.html Yes, the Git alternative to “fossil up 2016-08-01” is $ git checkout `git rev-list -n 1 --before=2016-08-01 master` …and it takes a long blog post to

Re: [fossil-users] Broke repository using command line.

2016-10-21 Thread Warren Young
On Oct 21, 2016, at 10:22 PM, Venkat Iyer wrote: > > Due to some ill-conceived advice and over-enthusiastic scripting Do you have some TH1 scripts (hooks, etc) installed? If so, can you share them? > fossil ticket set e9d34a2552 +icomment "ivenkat added on

Re: [fossil-users] Broke repository using command line.

2016-10-21 Thread Warren Young
On Oct 21, 2016, at 10:39 PM, Venkat Iyer wrote: > > Thanks for the reply. No TH1 scripts, no hooks. The only customization is > adding "assigned_to" in the ticket through the GUI. Actually, I can replicate this with a clean repo: mkdir x cd x f new

Re: [fossil-users] remote check in

2016-10-24 Thread Warren Young
On Oct 22, 2016, at 4:40 PM, Scott Doctor wrote: > > How do they do such over the internet without having command line access? Are you actually saying that your fellow researchers don’t have access to the command line on their own workstations? I do understand that some

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

2016-10-24 Thread Warren Young
On Oct 22, 2016, at 3:23 PM, K. Fossil user wrote: > > 1/ As I've stated in the past according to people I do know, for security > reason, inetd/xinetd is not recommended. I just did a search for inetd at the NVD CVE search, and got nothing relevant to

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

2016-10-24 Thread Warren Young
On Oct 22, 2016, at 5:55 PM, K. Fossil user wrote: > > >« Branches in Fossil are just auto-propagating tags » > This is what they've said, technically at least. > For me this is not how I want it to be, because for most people tags are not > branches Be

Re: [fossil-users] remote check in

2016-10-24 Thread Warren Young
On Oct 24, 2016, at 11:33 AM, Scott Doctor wrote: > > The issues I initially had with fossil were due to a misunderstanding about > how fossil works. An issue is that clicking the help button in the fossil UI > gives a wall of commands. If the repository’s /help URL is

Re: [fossil-users] windows compiling with MS VC

2016-10-24 Thread Warren Young
On Oct 24, 2016, at 2:08 PM, Warren Young <w...@etr-usa.com> wrote: > > On Oct 24, 2016, at 2:03 PM, jungle Boogie <jungleboog...@gmail.com> wrote: >> >> On 24 October 2016 at 11:44, jungle Boogie <jungleboog...@gmail.com> wrote: >>> Building zlib

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

2016-10-24 Thread Warren Young
On Oct 24, 2016, at 2:16 PM, Joerg Sonnenberger <jo...@bec.de> wrote: > > On Mon, Oct 24, 2016 at 09:56:45AM -0600, Warren Young wrote: >> The only common exception is this recent trend of replacing old, >> bloated software that grew organically over decades wi

Re: [fossil-users] windows compiling with MS VC

2016-10-24 Thread Warren Young
On Oct 24, 2016, at 2:03 PM, jungle Boogie wrote: > > On 24 October 2016 at 11:44, jungle Boogie wrote: >> Building zlib from "..\compat\zlib"... >> >>cl -c -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE >> -nologo -MD -W3 -O2

Re: [fossil-users] remote check in

2016-10-24 Thread Warren Young
On Oct 24, 2016, at 2:32 PM, Adam Jensen <han...@riseup.net> wrote: > > On 10/24/2016 03:07 PM, Warren Young wrote: >> I don’t know that Fossil is all that close to any other software >> system you’ve likely used before. > > Isn't it a file (version) manageme

Re: [fossil-users] remote check in

2016-10-24 Thread Warren Young
On Oct 24, 2016, at 2:59 PM, Warren Young <w...@etr-usa.com> wrote: > > There is an experimental (?) feature of Fossil allowing it to operate as a > FUSE filesystem. I’ve just peeked into the code for that, and it appears the Fossil fusefs feature is read-only. If someo

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

2016-11-14 Thread Warren Young
On Nov 12, 2016, at 4:52 AM, arnoldemu wrote: > > That is useful. What would the windows equivalent command-line? There really isn’t an equivalent because Windows has no equivalents to the key mechanisms used in Andy’s two commands: 1. Command substitution:

Re: [fossil-users] 'fossil server' unresponsive with high CPU usage

2016-11-14 Thread Warren Young
On Nov 14, 2016, at 12:32 AM, J. Cameron Cooper wrote: > > I've been happily using fossil for quite a few years now, but I recently had > an unusual symptom develop on one of my machines. I think it's a bug, but I > have no idea how to add a ticket on the main site, so I'll

Re: [fossil-users] fossil amend comment

2016-11-28 Thread Warren Young
On Nov 26, 2016, at 1:26 PM, Martin Gagnon wrote: > > On Sat, Nov 26, 2016 at 01:15:11PM +0100, arnoldemu wrote: >> >> I forced a submit with >> >> fossil commit --allow-empty > > Server get the change here, because the "commit" command does a "sync" > when autosync is

[fossil-users] Sync doesn't include non-artifact changes?

2016-11-28 Thread Warren Young
I’ve noticed that if I make a change to a non-artifact setting in the repository on a different machine that re-syncing does not give me a copy on my machine. Examples: - Skin changes - Ticket tracker customizations - Everything in Admin > Settings If I close the repo, re-clone, and reopen it

Re: [fossil-users] Sync doesn't include non-artifact changes?

2016-11-28 Thread Warren Young
On Nov 28, 2016, at 9:06 AM, Richard Hipp wrote: > >fossil all config pull all Thanks, that’s perfect! I care about this because I treat my local clones as off-site backups relative to the official central repos, and it’s not a very good backup if it’s incomplete. I do

Re: [fossil-users] fossil-users Digest, Vol 106, Issue 17

2016-11-15 Thread Warren Young
On Nov 14, 2016, at 10:09 PM, Ron W wrote: > > On Nov 12, 2016, at 4:52 AM, arnoldemu > wrote: > > > > That is useful. What would the windows equivalent command-line? > > 2. xargs. Again, no direct equivalent, requiring a bunch of ugly

Re: [fossil-users] 'fossil server' unresponsive with high CPU usage

2016-11-15 Thread Warren Young
On Nov 15, 2016, at 12:09 AM, J. Cameron Cooper wrote: > > after reinstalling [crtmpserver] today I don't see the issue anymore. It could have been a firewall issue, then, with the package’s post-install script restoring the proper port 8080 firewall rule, which also allows

Re: [fossil-users] fossil revert is not recursive?

2016-11-18 Thread Warren Young
On Nov 18, 2016, at 12:50 PM, arnoldemu wrote: > > So I am confused. If I can add recursive, why can't I do a revert recursive? Someone Has To Do It. But also, there are subtleties here. For example, from within a Fossil source code checkout: fossil rm

Re: [fossil-users] fossil reports erroneous revert?

2016-11-18 Thread Warren Young
On Nov 18, 2016, at 1:21 PM, arnoldemu wrote: > > Fossil reports "revert" but this is confusing because there is nothing to > revert. > > Is this expected? I don’t know about “expected,” but yes, that’s the way Fossil has worked as long as I’ve used it.

Re: [fossil-users] fossil revert is not recursive?

2016-11-18 Thread Warren Young
On Nov 18, 2016, at 1:40 PM, Warren Young <war...@etr-usa.com> wrote: > > On Nov 18, 2016, at 12:50 PM, arnoldemu <mem...@arnoldemu.freeserve.co.uk> > wrote: >> >> So I am confused. If I can add recursive, why can't I do a revert recursive? > > Someone

Re: [fossil-users] rebuild scale-ability/data written/repo size ratio

2016-10-31 Thread Warren Young
On Oct 30, 2016, at 1:57 AM, Karel Gardas <gard...@gmail.com> wrote: > > On Fri, Oct 28, 2016 at 7:02 PM, Warren Young <w...@etr-usa.com> wrote: >> On Oct 28, 2016, at 3:45 AM, Karel Gardas <gard...@gmail.com> wrote: >>> >>> make it more scale

Re: [fossil-users] Fossil on HN

2016-10-12 Thread Warren Young
On Oct 11, 2016, at 6:38 PM, K. Fossil user wrote: > > 1/ I ask for a poll If you mean your request nearly 4 months ago in the thread about how the mailing list is run, a poll isn’t going to affect anything. This project is not a democracy. Like virtually

Re: [fossil-users] markdown option missing in dropdown of tickets

2016-12-16 Thread Warren Young
On Dec 15, 2016, at 9:18 AM, Aldo Nicolas Bruno wrote: > > I see only: Wiki, HTML, plain-text and [links-only] That is a known-missing feature. I and others have wished for it here on the mailing list. All that’s needed is for someone to want it badly enough to write

Re: [fossil-users] Ticket description format is reset on edit

2016-12-13 Thread Warren Young
On Dec 13, 2016, at 1:56 AM, Francois Vogel wrote: > > When editing a fossil ticket, to add a new comment for instance, I have > noticed that the combobox showing the format of the ticket description (i.e. > the format of the original report) is reset to "Plain text"

Re: [fossil-users] db errors after Ctrl-C

2016-12-13 Thread Warren Young
On Dec 13, 2016, at 4:20 AM, rosscann...@fastmail.com wrote: > > I noticed a minor bug in fossil. Yeah, I think I agree. > I can do some detective work here Try this: add #error Yo! on line 891 of src/shell.c, immediately after the ifdef for SIGINT. I think you’ll find that it builds

Re: [fossil-users] Ticket description format is reset on edit

2016-12-13 Thread Warren Young
On Dec 13, 2016, at 10:57 AM, Francois Vogel wrote: > > Thank you for your answer. However changing the format of *comments* was not > my point. Rather I'm concerned with the automatic reset of the format *of the > original report* I am considering the original report to

Re: [fossil-users] Managing fossil project setup

2017-01-10 Thread Warren Young
On Jan 10, 2017, at 11:51 AM, Lutz Filor wrote: > > But I have problems when I want to propagate the new project. > a) The new user, can't logout nor login Your posted command line examples show using “fossil ui”, which means you’re logged in with the default user on the

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

2016-12-05 Thread Warren Young
On Dec 4, 2016, at 12:50 PM, Karel Gardas wrote: > > On Sun, Dec 4, 2016 at 5:28 AM, Martin Vahi wrote: >> It is about 4.4GiB, over 100k files, over 6k folders, >> but it should not be that bad. After all, that's what >> many projects look like in

Re: [fossil-users] How to ignore hidden folders

2017-01-04 Thread Warren Young
On Jan 4, 2017, at 11:39 AM, Scott Doctor wrote: > > How do I set a permanent ignore for hidden folders, or a specific folder? https://stackoverflow.com/questions/4491447/ ___ fossil-users mailing list

Re: [fossil-users] Running a Fossil server alongside Apache on Ubuntu

2017-01-04 Thread Warren Young
On Jan 4, 2017, at 12:06 PM, Damien Sykes-Lindley wrote: > > How do I update to the latest? $ mkdir -p ~/museum ~/fossil/trunk $ fossil clone http://fossil-scm.org ~/museum/fossil.fossil $ cd ~/fossil/trunk $ fossil open ~/museum/fossil.fossil $ ./configure && make

Re: [fossil-users] Adding binary files to fossil

2017-01-04 Thread Warren Young
On Jan 3, 2017, at 1:31 PM, Scott Doctor wrote: > > I added my binary files. Did not get any warning. Should I get a warning if > fossil detects that a file is binary? $ mkdir x $ cd x $ f init ../x.fossil $ f open ../x.fossil $ dd if=/dev/random of=x count=1k 1024+0

Re: [fossil-users] Adding binary files to fossil

2017-01-04 Thread Warren Young
On Jan 3, 2017, at 11:08 AM, Scott Doctor wrote: > > There are a few binary files that are needed to compile and use the program. If you’d care to share the details about those few binary files, we might be able to improve the way Fossil works for you. Eduard’s point

Re: [fossil-users] Running a Fossil server alongside Apache onUbuntu

2017-01-04 Thread Warren Young
On Jan 4, 2017, at 1:06 PM, Damien Sykes-Lindley wrote: > > What do I need to install to do this? First it complained that it couldn't > find GCC so I installed that, On Debian/Ubuntu type systems, it’s easiest to say “sudo apt install build-essential”. That

Re: [fossil-users] Question about the file formats.

2016-12-20 Thread Warren Young
On Dec 20, 2016, at 11:48 AM, John Found wrote: > > I know that fossil (and most other version control systems) can handle > properly > only text source files. Says who? There are some features of Fossil that simply don’t work when given a binary file, like “fossil

Re: [fossil-users] Question about the file formats.

2016-12-20 Thread Warren Young
On Dec 20, 2016, at 12:35 PM, John Found wrote: > > Under "fossil algorithms" I mean two (in my understanding most important in > what is called "version control": diff algorithm and 3-way merge algorithm. When I said that Fossil can’t diff two binary files, I meant that

Re: [fossil-users] Question about the file formats.

2016-12-20 Thread Warren Young
On Dec 20, 2016, at 3:57 PM, Warren Young <war...@etr-usa.com> wrote: > >> What if I design some text file format (containing only ascii characters) and >> it can't be properly processed by fossil? > > Then you should post it as a replicable test case for our study.

Re: [fossil-users] Introducing FossGit -- a new CLI tool for conveniently mirroring Fossil to Git.

2016-12-28 Thread Warren Young
On Dec 25, 2016, at 11:13 AM, Chad Perrin wrote: > > new utility called FossGit for > creating and maintaining Git mirrors of Fossil repositories: Does it cope with the fact that Fossil allows a given tag to appear multiple times in a repository but Git does not? In order

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

2017-03-27 Thread Warren Young
On Mar 26, 2017, at 11:49 AM, Tomasz Konojacki wrote: > > On Sun, 26 Mar 2017 19:25:25 +0200 > Christophe Gouiran wrote: > >> I see that most of you complain about this proposed feature. > > TBH, many members of this list live in the UNIX greybeard

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

2017-03-27 Thread Warren Young
On Mar 27, 2017, at 10:19 AM, Martin S. Weber wrote: > > On 03/27/17 01:55, Roy Marples wrote: >> Pager output disappearing with the pager (I assume when asking the pager to >> exit) is an issue with the pager. > > I disagree. Disappearing output uses the "alternate screen"

Re: [fossil-users] [PROPOSED FEATURE] Fossil 'branch' command displays only current branch by default

2017-03-27 Thread Warren Young
On Mar 27, 2017, at 11:50 AM, bch wrote: > > > executing "fossil branch" to get the current branch is not very convenient > > to me. > > Note that "fossil info" gives information about the current checkout, > including the branch name. That info is also given in

Re: [fossil-users] [PROPOSED FEATURE] Fossil 'branch' command displays only current branch by default

2017-03-27 Thread Warren Young
On Mar 27, 2017, at 12:07 PM, Warren Young <war...@etr-usa.com> wrote: > > It isn’t always clue to newbies s/clue/clear/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/lis

Re: [fossil-users] Command-line output format

2017-03-29 Thread Warren Young
On Mar 28, 2017, at 1:16 AM, Florian Balmer wrote: > > parsing JSON from shell scripts or Windows > batch files seems not so trivial. We have no lack of options for JSON parsing on POSIX type systems: https://unix.stackexchange.com/questions/ The top option, jq,

Re: [fossil-users] "CGI" command and argc

2017-03-29 Thread Warren Young
On Mar 28, 2017, at 1:16 AM, Florian Balmer wrote: > > #!./fossil cgi fossil.config That relies on behavior POSIX hasn’t specified: https://stackoverflow.com/questions/4303128/ What’s wrong with doing it the portable way? #!/bin/sh exec ./fossil cgi

Re: [fossil-users] Command-line output format

2017-03-29 Thread Warren Young
On Mar 29, 2017, at 8:40 AM, Warren Young <war...@etr-usa.com> wrote: > > https://unix.stackexchange.com/questions/ Oops, over-edited that URL: https://unix.stackexchange.com/questions/121718/ ___ fossil-users mailing list

Re: [fossil-users] Couple of beginner questions

2017-03-30 Thread Warren Young
On Mar 29, 2017, at 8:54 PM, Andy Bradford <amb-sendok-1493434470.mmjmhcdkgpnhiioca...@bradfords.org> wrote: > > Thus said Warren Young on Wed, 29 Mar 2017 14:25:34 -0600: > >> Any text editor or compiler that can't cope with UTF-8 in 2017 is >> broken or can be

Re: [fossil-users] Couple of beginner questions

2017-03-30 Thread Warren Young
On Mar 29, 2017, at 2:48 PM, The Tick <the.t...@gmx.com> wrote: > > On 3/29/2017 3:25 PM, Warren Young wrote: >> >> Any text editor or compiler that can’t cope with UTF-8 in 2017 is broken or >> can be ignored. > > I've been using vi for 40 years so tha

Re: [fossil-users] Couple of beginner questions

2017-03-30 Thread Warren Young
On Mar 30, 2017, at 8:34 AM, Stephan Beal <sgb...@googlemail.com> wrote: > > On Thu, Mar 30, 2017 at 4:30 PM, Warren Young <war...@etr-usa.com> wrote: > I don’t think it’s fair to notable Fossil users like Jörg Sonnenberger that > we misspell their names simply because we

Re: [fossil-users] Couple of beginner questions

2017-03-30 Thread Warren Young
On Mar 30, 2017, at 8:38 AM, Warren Young <war...@etr-usa.com> wrote: > > On Mar 29, 2017, at 2:48 PM, The Tick <the.t...@gmx.com> wrote: >> >> I've been using vi for 40 years so that's not going to change. > > I’ve “only” been using vi for about 37 ye

Re: [fossil-users] Couple of beginner questions

2017-03-30 Thread Warren Young
On Mar 29, 2017, at 2:47 PM, The Tick wrote: > > I also understand that a program script or, say, C source file can use the > utf-8 escape sequence to generate these characters when the program is run. > That is not possible in comments tho. I put © in C++ comments all the

Re: [fossil-users] Couple of beginner questions

2017-03-29 Thread Warren Young
On Mar 29, 2017, at 2:05 PM, The Tick wrote: > > On 3/29/2017 2:36 PM, Richard Hipp wrote: >> Most of the world is using UTF-8 now. > > I'm wondering how that can be for programming language source files. Existence proof:

Re: [fossil-users] Quick Q on valid markup for commit msgs

2017-03-31 Thread Warren Young
On Mar 30, 2017, at 11:34 PM, The Tick wrote: > > I went to admin->timeline and checked "allow block markup" > > I went to wiki->Formatting rules->Markdown wiki. According to an earlier post, it uses some variant on Fossil Wiki markup, not Markdown. It doesn’t seem to be

Re: [fossil-users] Unfortunately I still see blobs of text for commit messages

2017-03-31 Thread Warren Young
On Mar 30, 2017, at 9:32 PM, The Tick wrote: > > I don't know a lot about css but with the raw fossil html: > > that the CSS you gave refers to. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org

Re: [fossil-users] Couple of beginner questions

2017-03-31 Thread Warren Young
On Mar 31, 2017, at 1:42 PM, Andy Bradford wrote: > > You could have continued on the way you were > doing things. No need to change anything except tell your browser that > the content is not Unicode, but is instead ``Western'' or ISO-8895-1 or > something else.

Re: [fossil-users] Crash with this AMEND command

2017-03-17 Thread Warren Young
On Mar 17, 2017, at 5:59 PM, Tony Papadimitriou wrote: > > The following command crashes fossil (older and up to current version). Null pointer dereference on line 841 of src/file.c. ___ fossil-users mailing list

Re: [fossil-users] Cloning issue

2017-03-16 Thread Warren Young
On Mar 15, 2017, at 1:55 AM, Dan Raymond wrote: > > whenever I try to autosync back the other way I get a "not authorized to > write" error? That’s because you didn’t give your remote Fossil user name in the clone URL. Hence, you’re anonymous, hence you can’t write.

Re: [fossil-users] Cloning issue

2017-03-16 Thread Warren Young
On Mar 16, 2017, at 6:32 AM, Warren Young <war...@etr-usa.com> wrote: > > On Mar 15, 2017, at 1:55 AM, Dan Raymond <d...@ecourban.com.au> wrote: >> >> whenever I try to autosync back the other way I get a "not authorized to >> write" error? > &g

Re: [fossil-users] Crash with this AMEND command

2017-03-20 Thread Warren Young
On Mar 18, 2017, at 11:59 PM, Andy Bradford wrote: > > Thus said "Tony Papadimitriou" on Sat, 18 Mar 2017 01:59:21 +0200: > >> The following command crashes fossil (older and up to current >> version). > > It doesn't crash for me. It didn’t crash for me

Re: [fossil-users] Cloning issue

2017-03-16 Thread Warren Young
On Mar 16, 2017, at 3:04 PM, Dan Raymond wrote: > > Whats not clear in the docs is which password. That’s because it depends. :) If you use an ssh:// URL, you give the OS user password because the local Fossil logs into the remote system and schleps the data back through

Re: [fossil-users] Fossil_v_2_0 Bug: Abandoning commit due to long lines in Foo

2017-03-21 Thread Warren Young
On Mar 21, 2017, at 5:49 PM, Martin Vahi wrote: > > I tried to commit the batch of small files > individually. No luck: The error tells you why: > ...facebook.html > contains long lines. Use --no-warnings or the "binary-glob" setting to > disable this warning. >

Re: [fossil-users] Is Fossil Hash-collision proof?

2017-03-21 Thread Warren Young
On Mar 21, 2017, at 11:04 PM, Martin Vahi wrote: > > I haven't encountered any collisions yet Nor are you likely to by accident, ever. The only reason it’s even a concern is that a motivated attacker with lots of money could force a collision with the old SHA-1

Re: [fossil-users] REST API and client for same

2017-04-04 Thread Warren Young
On Apr 4, 2017, at 11:24 AM, Paul Hammant wrote: > > > I have little need for such a thing myself, so I’m just throwing this idea > > out > > there for anyone who thinks it looks like a good itch to scratch. > > I do have a need for this class of use. My thread "Fossil as an

Re: [fossil-users] REST API and client for same

2017-04-03 Thread Warren Young
On Apr 3, 2017, at 1:29 AM, Stephan Beal wrote: > > Commits can't be done without a checkout Given a way to ask Fossil over HTTP for the set of artifacts that makes up $reference, where the latter is anything Fossil currently accepts in “fossil up $reference” you’ll

Re: [fossil-users] SSL on Mac

2017-04-04 Thread Warren Young
On Apr 3, 2017, at 6:13 PM, J. Cameron Cooper wrote: > > SSL: cannot connect to host chiselapp.com:443 () That generally means the server has tightened down its rules on what it will accept for an SSL connection: dropping old, broken, versions of the protocol, dropping

Re: [fossil-users] XSS attack and fossil hosting services

2017-04-03 Thread Warren Young
On Apr 2, 2017, at 9:28 PM, Eduard wrote: > > An attacker can place malicious javascript at the top of every page Certainly. > they could, for example, change the victim's password Doesn’t the login cookie prevent the hosted user from doing that to any but

Re: [fossil-users] XSS attack and fossil hosting services

2017-04-03 Thread Warren Young
On Apr 3, 2017, at 11:15 AM, Eduard wrote: > > Evil-user then convinces > good-user to visit evilproject while logged into goodproject Ah, I see. Yes, I agree now. >>> (Another way to fix it is by giving each repository a separate subdomain >> >> ...run as a

[fossil-users] REST API and client for same

2017-04-02 Thread Warren Young
In a conversation off-list, I had an idea that might solve several existing problems. What if the current HTTP URL interface of Fossil were expanded to be able to do everything that Fossil internally can do, such that it eventually implements REST API interface that is functionally equivalent

Re: [fossil-users] REST API and client for same

2017-04-02 Thread Warren Young
On Apr 2, 2017, at 2:48 PM, Stephan Beal wrote: > > a) that's essentially what the JSON API is …minus the lightweight Subversion-like client, of course. But, it’s good to know that most of the work is already done. > with the notable exception of missing blob support

Re: [fossil-users] Couple of beginner questions

2017-04-05 Thread Warren Young
On Apr 4, 2017, at 7:02 PM, Ross Berteig wrote: > > So I accidentally wrote a blog post about the experiment. Thank you for doing the research, and writing it up. Bottom line for the Fossil end of things, UTF-8 is a thing of such pragmatic beauty that it is almost never

[fossil-users] The SHA3 transition as firewall

2017-03-09 Thread Warren Young
Premise: Depending on the ROI in each specific case, SHA1 is either broken today or will be broken at some indefinite (but finite) time in the future. The cost of attack will continue to decrease for many years to come, so the number of repositories in danger of attack will continue increase.

Re: [fossil-users] setting hash-policy via web UI

2017-03-09 Thread Warren Young
On Mar 9, 2017, at 2:59 PM, Richard Hipp wrote: > > The "fossil new" command creates an initial, empty check-in which is > suppose to become the ancestor of all future check-ins. That check-in > will have a SHA3 hash, unless you use the --sha1 option on "fossil > new”. Maybe

Re: [fossil-users] setting hash-policy via web UI

2017-03-09 Thread Warren Young
On Mar 9, 2017, at 2:24 PM, Richard Hipp wrote: > > On 3/9/17, Eduard wrote: >> >> Are there plans to expose the 'hash-policy' configuration option for >> modification in the fossil web interface? > > No. I was hoping to avoid yet another

Re: [fossil-users] The SHA3 transition as firewall

2017-03-09 Thread Warren Young
On Mar 9, 2017, at 1:03 PM, Richard Hipp wrote: > > If a new artifact Y' which has the > same SHA1 hash as Y comes along, it will be discarded, since an > artifact with that same hash is already in the repository. That can be gotten around with a MITM attack, as I’ve already

Re: [fossil-users] setting hash-policy via web UI

2017-03-09 Thread Warren Young
On Mar 9, 2017, at 3:00 PM, Warren Young <war...@etr-usa.com> wrote: > > Maybe then just a notice in Admin > Configuration or similar: “Hey, you know > you’ve got a repo that Fossil 1.x can’t read, right? Just checking.” It could be conditional based on the repository age,

Re: [fossil-users] The SHA3 transition as firewall

2017-03-09 Thread Warren Young
On Mar 9, 2017, at 1:44 PM, Andy Bradford <amb-sendok-1491684247.nblmjmfmonahnenbi...@bradfords.org> wrote: > > Thus said Warren Young on Thu, 09 Mar 2017 13:37:35 -0700: > >> That can be gotten around with a MITM attack > > How? If the server to which the att

Re: [fossil-users] setting hash-policy via web UI

2017-03-09 Thread Warren Young
On Mar 9, 2017, at 2:54 PM, Richard Hipp <d...@sqlite.org> wrote: > > On 3/9/17, Warren Young <war...@etr-usa.com> wrote: >> Our newbie may be setting up a repo that >> they know needs to be accessible to Fossil 1.x clients, and they can’t force >> the upgra

Re: [fossil-users] setting hash-policy via web UI

2017-03-09 Thread Warren Young
On Mar 9, 2017, at 3:11 PM, sky5w...@gmail.com wrote: > > I am asking since I would prefer to create new repo's with sha3 now using > fossil 2.1. That’s what you will get by default. You have to go out of your way with Fossil 2.1+ to get a new SHA-1 based repo. > Then figure how to

Re: [fossil-users] The SHA3 transition as firewall

2017-03-09 Thread Warren Young
Just to clarify my prior reply: my criticisms of points 1 and 3 do not undermine my support for the solution, which is in points 2, 4, and 5. I’m just saying that I’d rather you didn’t bring such things up, as they are obfuscatory arguments at best. It is sufficient to argue the strength of

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

2017-03-03 Thread Warren Young
On Mar 3, 2017, at 6:29 AM, Richard Hipp wrote: > > (1) When creating a new check-in, use the hash algorithm (SHA1 or > SHA3) that is used by the primary parent check-in. I’m not certain what “primary” means in this context. I assume that it’s a distinction for cases where

Re: [fossil-users] Fossil Version 2.0

2017-03-03 Thread Warren Young
On Mar 3, 2017, at 5:07 PM, Warren Young <war...@etr-usa.com> wrote: > > bootstrapping via Fossil itself is no longer one of them on Debian for the > next few years. On re-reading that, I see that it’s not as clear as it should be. When I said bootstrapping with Fossil was

Re: [fossil-users] Fossil Version 2.0

2017-03-03 Thread Warren Young
On Mar 3, 2017, at 6:45 AM, Richard Hipp wrote: > > Fossil version 2.0 is now available on the Fossil website > we will publish new versions of Fossil that actually generate SHA3-256 hashes. I presume you will also be dogfooding it on fossil-scm.org, complete with moving to

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

2017-03-03 Thread Warren Young
On Mar 3, 2017, at 5:49 PM, Ron W wrote: > > I would argue that wiki pages, ticket changes and ticket attachments have > parent artfacts. For wiki pages, it would be the most commit of that page. Okay, but what about new wiki pages? What is *their* parent? Ditto new

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

2017-03-03 Thread Warren Young
On Mar 3, 2017, at 5:58 PM, Warren Young <war...@etr-usa.com> wrote: > > Ditto new tickets and new tech notes. Tech notes are tied to a particular checkin, aren’t they? So never mind on that one. ___ fossil-users mailing list

Re: [fossil-users] Fossil 2.1 menu scrunch.

2017-03-08 Thread Warren Young
On Mar 8, 2017, at 9:07 AM, sky5w...@gmail.com wrote: > > Yeah, I'm just pointing out a change from v2.0 and down. Are you sure it’s a change to the default Fossil skin? I’m a bit blinkered when it comes to such things, since I always customize the skin, so my Fossil skins never change from

Re: [fossil-users] Support for commonmark markdown in fossil

2017-03-13 Thread Warren Young
On Mar 11, 2017, at 7:07 AM, Mark Janssen wrote: > > the fossil markdown support is fairly limited (for example there are no code > blocks) We must have different definitions of “code block.” This is a Fossil wiki page with a very large code block down at the end:

Re: [fossil-users] The SHA3 transition as firewall

2017-03-10 Thread Warren Young
On Mar 10, 2017, at 2:53 AM, Joerg Sonnenberger <jo...@bec.de> wrote: > > On Thu, Mar 09, 2017 at 01:37:35PM -0700, Warren Young wrote: >> >> >> That can be gotten around with a MITM attack > > It still only matters if you can *introduce* objects. You’

Re: [fossil-users] Fossil 2.1

2017-03-10 Thread Warren Young
On Mar 10, 2017, at 10:26 AM, Richard Hipp wrote: > > Fossil version 2.1 is now available from the download pages. …after 9 days from first commit to final release. Beat that, Git! ___ fossil-users mailing list

Re: [fossil-users] Support for commonmark markdown in fossil

2017-03-13 Thread Warren Young
On Mar 13, 2017, at 10:32 AM, Natacha Porté <nata...@instinctive.eu> wrote: > > on Monday 13 March 2017 at 09:50, Warren Young wrote: >> I have found bugs in Fossil’s Markdown implementation. For example, it >> doesn’t deal properly with hyperlinks to Wiki

Re: [fossil-users] Fossil 2.1 menu scrunch.

2017-03-08 Thread Warren Young
On Mar 7, 2017, at 9:58 AM, sky5w...@gmail.com wrote: > > But, the scrunch appears with no scrollbar. I’m not sure what behavior you’re expecting, but what I see looks like perfectly sane HTML rendering behavior. There isn’t enough room for “Download”, its padding, or the separator that’s

Re: [fossil-users] Support for commonmark markdown in fossil

2017-03-13 Thread Warren Young
On Mar 13, 2017, at 12:57 PM, Martin S. Weber <ephae...@gmx.net> wrote: > > On 03/13/17 19:00, Warren Young wrote: >> On Mar 13, 2017, at 10:32 AM, Natacha Porté <nata...@instinctive.eu> wrote: >>> Or do you expect it to count parentheses and prevent y

<    1   2   3   4   5   6   7   8   9   10   >