diff options
| author |   Michał Górny <mgorny@gentoo.org> | 2017-06-15 09:27:47 +0200 |
|---|---|---|
| committer | Michał Górny <mgorny@gentoo.org> | 2017-06-15 19:15:05 +0200 |
| commit | e6abcc0b7cbdca481862a5c7cca946c01c471ffb (patch) | |
| tree | 5b9eafad04015fbda786e08b9d2e39eec14a12ab | |
| parent | const: Remove unused MANIFEST1_REQUIRED_HASH (diff) | |
| download | portage-e6abcc0b7cbdca481862a5c7cca946c01c471ffb.tar.gz portage-e6abcc0b7cbdca481862a5c7cca946c01c471ffb.tar.bz2 portage-e6abcc0b7cbdca481862a5c7cca946c01c471ffb.zip | |
const: Change the MANIFEST2_REQUIRED_HASH to SHA512
Following the plan established in GLEP 59, we're long overdue
deprecating SHA256. Since we have finally got rid of the last packages
lacking SHA512 checksums, we can proceed with that. In order to prepare
for it, however, we need to change the required hash to SHA512 and make
sure developers install the new Portage & repoman versions first.
Of course, a better course of action would be to kill
MANIFEST2_REQUIRED_HASH entirely and make Portage capable of dealing
with any hash set. However, that's a larger piece of work and it would
delay the immediate goal.
Reviewed-by: Zac Medico <zmedico@gentoo.org>
| -rw-r--r-- | pym/portage/const.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/pym/portage/const.py b/pym/portage/const.py index 052d4ca2f..cbd2b6042 100644 --- a/pym/portage/const.py +++ b/pym/portage/const.py @@ -234,7 +234,7 @@ MANIFEST2_HASH_FUNCTIONS = ("SHA256", "SHA512", "WHIRLPOOL", "BLAKE2B", "BLAKE2S", "SHA3_256", "SHA3_512", "STREEBOG256", "STREEBOG512") MANIFEST2_HASH_DEFAULTS = frozenset(["SHA256", "SHA512", "WHIRLPOOL"]) -MANIFEST2_REQUIRED_HASH = "SHA256" +MANIFEST2_REQUIRED_HASH = "SHA512" MANIFEST2_IDENTIFIERS = ("AUX", "MISC", "DIST", "EBUILD") |