Hi Richard, >The "auto" hash-policy automatically flips to "sha3" as soon as Fossil >sees one or more SHA3 artifacts in the repo. Since your repo contains >SHA3 artifacts, you won't be able to set the policy to "auto" because >it will immediately and automatically flip to "sha3". > >That is the way "auto" is designed to work. I expected it to automatically do that when I did a "fossil update" and get the files provided I had fossil 2.1 installed. I have autosync set and I thought that would then sync from the server and automatically switch to sha3 and get the new files.
>How were you expecting it to work? How can the documentation be improved? Setting the hash policy was fine that worked without confusion. When I then accessed the remote repository from another machine I expected it to automatically see the change and automatically switch the client to the new policy. If the client needed to be updated then ideally fossil client should tell me. It would have been great if this is what had happened: >fossil update Autosync: http://xxxx/arnold Autosync failed. This fossil repository is not compatible with the version of your client. You need version 2.1 or later. Please visit http://www.fossil-scm.org and download a new client. Then after installing the new client and with the hash-policy set to auto: >fossil update Autosync: http://xxxx/arnold Hash-policy on server has been updated to sha3. Switching to sha3 for client. ... <- normal sync here with cards and files listed. If I had set the policy to sha1 or other: >fossil update Autosync: http://xxxx/arnold Autosync failed. The fossil repository is using sha3 hash policy. Please set hash-policy to sha3 or use auto. Maybe for now, instead of (or in addition) to the errors I saw it could give a command to try to resolve the issue such as one that causes the database to update. Thank you Kevin
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
