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

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

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

I haven't encountered any collisions yet, but I was wondering, what will happen, if 2 different files that have the same size, same timestamps, different bitstreams, but the same hash (regardless of hash algorithm) were to be committed simultaneously, at the same commit? After all, it's the

Re: [fossil-users] Bugs in file_wd_isdir()

Joe Mistachkin wrote: Perhaps changing the exec-rel-paths setting might impact this? Not sure without further research. The bug has nothing to do with exec-rel-paths. The --command option simply forces the creation of a temporary directory, which is what triggers the bug on macOS (due to

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

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] Fossil_v_2_0 Bug: Abandoning commit due to long lines in Foo

On 3/21/17, Martin Vahi wrote: > > P.S. Right after sending my previous Bug report > to this list, like, literally in 10 seconds, > I received a spam email that used my own subject > line with the "Re:" prefix as its email subject. From "Eboni"? I'm very sorry about

Re: [fossil-users] Bugs in file_wd_isdir()

Perhaps changing the exec-rel-paths setting might impact this? Not sure without further research. Sent from my iPhone https://urn.to/r/mistachkin > On Mar 21, 2017, at 12:50 PM, Reimer Behrends wrote: > > Richard Hipp wrote: >> I wonder if you could provide a more

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

I unpakced the stblob that I tried to commit at the case that I described at my previous bug report and I tried to commit the batch of small files individually. No luck: ---citation--start

Re: [fossil-users] Using child projects/repositories effectively

On 3/21/2017 6:52 AM, Richard Hipp wrote: Apparently I checked that feature in. But I don't remember doing it. I do not use it myself and do not remember how it works. Maybe you can look at the source code and figure it out, and write up some improved documentation for us? And some test

Re: [fossil-users] Bugs in file_wd_isdir()

Richard Hipp wrote: I wonder if you could provide a more concrete example of the problem, perhaps in a the form of a "fossil test-file-environment" command that gives an incorrect answer? I'm afraid not. As I recall, the reason I ran into this originally was because "fossil diff --checkin

Re: [fossil-users] Using child projects/repositories effectively

Apparently I checked that feature in. But I don't remember doing it. I do not use it myself and do not remember how it works. Maybe you can look at the source code and figure it out, and write up some improved documentation for us? On 3/21/17, John P. Rouillard wrote:

[fossil-users] Using child projects/repositories effectively

Hi Everybody: I am currently using a child project/repository as described in: http://www.fossil-scm.org/index.html/doc/trunk/www/childprojects.wiki In this child repo I have files that should not be pushed to the main repo. So my locally added files, configuration file changes etc. all

Re: [fossil-users] Bugs in file_wd_isdir()

On 3/21/17, Reimer Behrends wrote: > The function file_wd_isdir() seems to have a number of bugs when used > with symbolic links. This manifests on macOS in particular (where /tmp > links to private/tmp – note that the link is relative), when temporary > directories are

[fossil-users] Bugs in file_wd_isdir()

The function file_wd_isdir() seems to have a number of bugs when used with symbolic links. This manifests on macOS in particular (where /tmp links to private/tmp – note that the link is relative), when temporary directories are created, e.g. for "fossil diff --checkin ...". * Relative links

Re: [fossil-users] Fossil_v_2_0 Bug: SQLITE_TOOBIG when Committing 1.6GiB size file

By recompiling with SQLITE_MAX_LENGTH=20 or so, you might be able to get a little more size out of Fossil. But the underlying SQLite storage is size limited to 2GB blobs, so beyond that, Fossil just wont work. And it will stop being efficient long before you get into giga-byte sized

[fossil-users] Fossil_v_2_0 Bug: SQLITE_TOOBIG when Committing 1.6GiB size file

--citation--start- ./wiki_references/2017/software/2017_03_21_maidsafe_net_tar_gz/f59c44f4cfae80319685fc8abdbc374039c22b421141951ai_278e5c783e9d982543415b569b6095bde7f1e409077208c4bb6bc48ee3fefe3fh_0481949961s_1000v.stblob contains binary data. Use --no-warnings or the "binary-glob"