| 1 |
+1 overall, just one timeline clarification. |
| 2 |
|
| 3 |
On Mon, Nov 06, 2017 at 05:58:21PM +0100, Michał Górny wrote: |
| 4 |
> T + 7 days |
| 5 |
> ---------- |
| 6 |
> Set: |
| 7 |
> manifest-hashes = BLAKE2B SHA512 |
| 8 |
> manifest-required-hashes = SHA512 |
| 9 |
> |
| 10 |
> New Manifest entries will use the new hashes but Portage will keep the |
| 11 |
> old hash set whenever it would need to refetch old distfiles. |
| 12 |
Query: |
| 13 |
Do we need to wait for it to be stable before making this change? |
| 14 |
Shouldn't old stable versions of Portage continue to verify SHA512 fine? |
| 15 |
Mostly I think devs need to be using a new enough Portage that can |
| 16 |
generate the BLAKE2B entries, but it shouldn't impact user Portage |
| 17 |
versions. |
| 18 |
|
| 19 |
-- |
| 20 |
Robin Hugh Johnson |
| 21 |
Gentoo Linux: Dev, Infra Lead, Foundation Asst. Treasurer |
| 22 |
E-Mail : robbat2@g.o |
| 23 |
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 |
| 24 |
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136 |
Archives