On 3/12/2017 10:50 AM, Richard Hipp wrote:
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.
I have a build on a x86_64 Linux box at my web host, which I
bootstrapped on that box originally by building from one of the source
tarballs, then cloned the fossil repo and rebuilt from the repo. My
installed fossil was sitting at v1.36, and I'd like to bring it up to
2.1 or later.
The other day I had updated my clone to version 2.0 and built, but had
not installed yet. So I installed it, then attempted to update to tip of
trunk. That failed:
[rosber15@aardwolf]$ fossil update trunk
Autosync: http://fossil-scm.org/
Round-trips: 1 Artifacts sent: 0 received: 0
SQLITE_CONSTRAINT: abort at 14 in [INSERT INTO
blob(rcvid,size,uuid,content)VALUES(0,-1,:uuid,NULL)]: CHECK constraint
failed: blob
fossil: SQL error: CHECK constraint failed: blob
[rosber15@aardwolf]$
Before panicking, I did fossil rebuild and tried again, mostly because
of what seemed like a database schema issue. Now fossil update trunk
succeeds.
So to move an existing project to the latest fossil after an SHA3-named
artifact exists, it appears to be necessary to rebuild existing repos
with version 2.0 or later so the database schema don't include a
constraint that forbids SHA3 names.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
