Re: [fossil-users] trouble cloning current fossil-scm.org repo with old fossil (2015)

2017-12-11 Thread Andy Bradford
Thus said Warren Young on Mon, 11 Dec 2017 14:53:37 -0700:

> To clarify the clarification, ``SHA256''  and ``SHA3-256'' are not the
> same thing, though they are sometimes confused.

And that is precisely why I called it a major correction. We're not even
in the same family of SHA algorithms now.

Andy
-- 
TAI64 timestamp: 40005a2f7625


___
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] trouble cloning current fossil-scm.org repo with old fossil (2015)

2017-12-11 Thread Warren Young
On Dec 10, 2017, at 7:40 PM, Andy Bradford  wrote:
> 
> Thus said Richard Hipp on Sun, 10 Dec 2017 19:20:59 -0500:
> 
>> Minor  correction:  the  hash  algorithm  changes  was  from  SHA1  to
>> SHA3-256.
> 
> I would call that a major correction! I knew something didn't seem right
> about what I sent…

To clarify the clarification, “SHA256” and “SHA3-256” are not the same thing, 
though they are sometimes confused.  “SHA256” should only be used to refer to 
the 256-bit variant of SHA-2, which like SHA-3, was standardized in several 
variants with different hash sizes.  Thus drh’s choice of terminology: 
“SHA3-256”.
___
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] trouble cloning current fossil-scm.org repo with old fossil (2015)

2017-12-10 Thread Andy Bradford
Thus said Richard Hipp on Sun, 10 Dec 2017 19:20:59 -0500:

> Minor  correction:  the  hash  algorithm  changes  was  from  SHA1  to
> SHA3-256.

I would call that a major correction! I knew something didn't seem right
about what I sent...

Thanks,

Andy
-- 
TAI64 timestamp: 40005a2df05f


___
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] trouble cloning current fossil-scm.org repo with old fossil (2015)

2017-12-10 Thread Richard Hipp
On 12/10/17, Andy Bradford  wrote:
> artifact IDs  have changed  from MD5
> hashes to SHA256 hashes

Minor correction: the hash algorithm changes was from SHA1 to
SHA3-256.  SHA1 is still supported, but the Fossil self-hosting repo
now uses SHA3 for newer check-ins, so you need a newer version of
Fossil to clone it.

-- 
D. Richard Hipp
d...@sqlite.org
___
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] trouble cloning current fossil-scm.org repo with old fossil (2015)

2017-12-10 Thread Michai Ramakers
On 10 December 2017 at 17:57, Andy Bradford  wrote:
> Thus said Michai Ramakers on Sun, 10 Dec 2017 16:21:02 +0100:
>
>> michai@work-lap:/tmp/f/f$ f ver
>> This is fossil version 1.33 [b00e60194e] 2015-08-22 12:42:15 UTC
>
> Since then  Fossil has had  much development.  In this case,  the change
> that is  breaking you  is that  the artifact IDs  have changed  from MD5
> hashes to SHA256 hashes and older versions of Fossil cannot handle them.
> You'll  have  to  ``bootstrap''  your repo  by  downloading  the  source
> directly from Fossil (zip format) and installing from there:
>
> http://www.fossil-scm.org/index.html/zip
>
> Or you could get a precompiled:
>
> http://www.fossil-scm.org/index.html/uv/download.html

Thanks, that makes it clear. I used/built from a .tgz from
fossil-scm.org, works fine. Just wondered why.

Michai
___
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] trouble cloning current fossil-scm.org repo with old fossil (2015)

2017-12-10 Thread Andy Bradford
Thus said Michai Ramakers on Sun, 10 Dec 2017 16:21:02 +0100:

> michai@work-lap:/tmp/f/f$ f ver
> This is fossil version 1.33 [b00e60194e] 2015-08-22 12:42:15 UTC

Since then  Fossil has had  much development.  In this case,  the change
that is  breaking you  is that  the artifact IDs  have changed  from MD5
hashes to SHA256 hashes and older versions of Fossil cannot handle them.
You'll  have  to  ``bootstrap''  your repo  by  downloading  the  source
directly from Fossil (zip format) and installing from there:

http://www.fossil-scm.org/index.html/zip

Or you could get a precompiled:

http://www.fossil-scm.org/index.html/uv/download.html

Andy
-- 
TAI64 timestamp: 40005a2d6798


___
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] trouble cloning current fossil-scm.org repo with old fossil (2015)

2017-12-10 Thread Michai Ramakers
On 10 December 2017 at 16:15, Michai Ramakers  wrote:
>
> Is it normal that I can't seem to clone the fossil-scm.org repo using
> this old version?

Apparently I have been living under a rock. I also seem to be unable
to open the cloned (using current trunk) fossil-scm.org repo using the
old fossil-binary (from 2015) - contents are missing afterwards:

michai@work-lap:/tmp/f/f$ f open ../f.fossil
project-name: Fossil
repository:   /tmp/f/f/../f.fossil
local-root:   /tmp/f/f/
config-db:/home/michai/.fossil
project-code: CE59BB9F186226D80E49D1FA2DB29F935CCA0333
check-ins:11026
michai@work-lap:/tmp/f/f$ ls -al
total 72
drwxr-xr-x 2 michai michai   100 Dec 10 16:10 .
drwxr-xr-x 3 michai michai80 Dec 10 16:07 ..
-rw-r--r-- 1 michai michai  7168 Dec 10 16:10 .fslckout
-rw-r--r-- 1 michai michai 60201 Dec 10 16:10 manifest
-rw-r--r-- 1 michai michai41 Dec 10 16:10 manifest.uuid
michai@work-lap:/tmp/f/f$
michai@work-lap:/tmp/f/f$ f ver
This is fossil version 1.33 [b00e60194e] 2015-08-22 12:42:15 UTC

Thanks again,
Michai
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] trouble cloning current fossil-scm.org repo with old fossil (2015)

2017-12-10 Thread Michai Ramakers
Hi,

I haven't tracked trunk since end of 2015.

Is it normal that I can't seem to clone the fossil-scm.org repo using
this old version?

michai@work-lap:/tmp/fold$ f ver
This is fossil version 1.33 [b00e60194e] 2015-08-22 12:42:15 UTC
michai@work-lap:/tmp/fold$ f clone https://www.fossil-scm.org/ f.fossil
Round-trips: 2   Artifacts sent: 0  received: 5949
malformed cfile line
Round-trips: 3   Artifacts sent: 0  received: 9505
Clone done, sent: 711  received: 8971582  ip: 45.33.6.223
server returned an error - clone aborted
michai@work-lap:/tmp/fold$

Cloning using current trunk (a0001dcf57) works fine.

Thanks,
Michai

-- 
Web: http://sheep-thrills.net/
Twitter: https://twitter.com/MichaiRamakers
LinkedIn: http://nl.linkedin.com/in/michai
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users