Hi, So here's my proposed plan, after considering all the replies.
Immediately after accepting --------------------------- a. Revbump Portage to add pyblake2 dep (to ensure BLAKE2 is supported on py<3.6) and request stabilizing this version. b. Create a git update hook that rejects Manifest entries that contain SHA512 only, to prevent a bug in current versions of Portage, that causes it to skip BLAKE2 when no implementation is installed instead of complaining [optional]. Now, let T = day when the new version is stable on amd64. T + 7 days ---------- Set: manifest-hashes = BLAKE2B SHA512 manifest-required-hashes = SHA512 New Manifest entries will use the new hashes but Portage will keep the old hash set whenever it would need to refetch old distfiles. T + 3 months ------------ Set: manifest-required-hashes = BLAKE2B Portage will now request updating hashes for all files, including old distfiles. We will start proactively updating Manifests here, and file bugs for fetch-restricted packages. T + 6 months ------------ All Manifests should use the new hashes by this time. The remaining fetch-restricted packages should be last-rited. T + 36 months ------------- Set: manifest-hashes = BLAKE2B Remove SHA512 from all Manifests. -- Best regards, Michał Górny
