Ah, I see. It seems strange to me that the policy didn't get set when I cloned. How can I avoid the same thing in the future and is there any way to change the artifacts in the local repository to SHA3?
On Wed, Nov 29, 2017, 05:39 Richard Hipp <d...@sqlite.org> wrote: > On 11/28/17, Jacob MacDonald <jaccar...@gmail.com> wrote: > > > > While the Chisel page says shun-sha1 is on, > > That could be a problem. That means chisel is rejecting any SHA1 > artifacts. The only want to change that is via command-line - there > is no web interface to set the hash policy. The command is: "fossil > hash-policy sha3" > > -- > 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 >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
