1 |
As reported in bug 131293 a pycrypto bug caused a lot of digest and |
2 |
Manifest files to be created with bogus sha256 hashes. A fixed |
3 |
pycrypto (2.0.1-r5) was committed to the tree. This means the |
4 |
following: |
5 |
|
6 |
- If you run ~arch portage and the latest pycrypto you will hit digest |
7 |
failures. You will hit fewer digest failures as packages are fixed. |
8 |
- If you run ~arch portage and do not upgrade pycrypto you will hit |
9 |
more and more digest issues as stuff is fixed. |
10 |
- If you run stable portage you are not affected. |
11 |
|
12 |
If you commit to the tree with an unfixed pycrypto you can add new |
13 |
broken digests, so please do not do that. |
14 |
|
15 |
We (portage project) are fixing known broken Manifests/digests. If you |
16 |
come across any broken SHA256 digests feel free to fix them though: |
17 |
the package is basically unusable with ~arch portage until it is |
18 |
fixed, and fixing it twice does not really hurt :) |
19 |
|
20 |
Apologies for the inconvenience. |
21 |
|
22 |
-- |
23 |
Marien. |