| 1 |
On 07/02/2012 03:52 AM, Alec Warner wrote: |
| 2 |
> On Sun, Jul 1, 2012 at 1:17 PM, Jeff Horelick <jdhore@g.o> wrote: |
| 3 |
>> As of Wednesday, July 4, 2012 at approximately 10:00 UTC, the manifest |
| 4 |
>> hashes used on the gentoo-x86 tree will change to "SHA256 SHA512 |
| 5 |
>> WHIRLPOOL". To facilitate this change, developers MUST be using at |
| 6 |
>> least portage-2.1.10.49 (or portage-2.2_alpha89), or, if your |
| 7 |
>> dev-lang/python is built with USE="-ssl", portage-2.1.10.51 (or |
| 8 |
>> portage-2.2_alpha95) or later is required. |
| 9 |
>> |
| 10 |
>> For users, if they are on a older portage, it will gracefully |
| 11 |
>> downgrade. For developers, however, not using a supported version will |
| 12 |
>> cause tree inconsistencies. Developers will also need to make sure |
| 13 |
>> they cvs up metadata/layout.conf (or cvs up the entire tree) after |
| 14 |
>> this change occurs before making any commits. |
| 15 |
>> |
| 16 |
>> Thanks |
| 17 |
>> |
| 18 |
> |
| 19 |
> Why don't we just reject manifests with old hashes? |
| 20 |
|
| 21 |
If we do that then we should only do it for *new* distfiles, because it |
| 22 |
will take some time for the new hashes to be generated for all of the |
| 23 |
existing files. By allowing the digests to be updated gradually, it's |
| 24 |
friendlier to committers since they aren't suddenly forced to download a |
| 25 |
bunch of distfiles just to generate the new digests. |
| 26 |
-- |
| 27 |
Thanks, |
| 28 |
Zac |
Archives