1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
James Cloos wrote: |
5 |
> I'm getting an inordinate number of masked- by corruption failures |
6 |
> since merging portage-2.1.2_rc3-r7. |
7 |
|
8 |
Do you get a "!!! Digest verification failed:" message before that, |
9 |
or only the "masked by: corruption" message? Assuming that the |
10 |
messages are invalid, you may be able to use FEATURES="-strict" or |
11 |
FEATURES="digest" to avoid those messages. However, you should know |
12 |
exactly what those features do before you change them. |
13 |
|
14 |
> Part of the problem is the addition of the complete dep graph. (Which |
15 |
> makes testing extraordinarily and horrifically painful; it now takes |
16 |
> emerge(1) about 20 to 30 minutes to get started, since reading in |
17 |
> everything in /var/db/pkg thrashes the dcache....) It is unable to |
18 |
> deal with some of the stuff already installed. |
19 |
|
20 |
It sounds like you're experiencing this bug: |
21 |
|
22 |
https://bugs.gentoo.org/show_bug.cgi?id=158649 |
23 |
|
24 |
I'll get that one fixed ASAP. |
25 |
|
26 |
> The "corruption" is not changed files. Hashes of the ebuilds always |
27 |
> match the srings in the Manifest files. It seems that it just doesn't |
28 |
> like old syntax. |
29 |
> |
30 |
> Running with --debug did not explain what it found to be "corrupt". |
31 |
> |
32 |
> I don't see any relevant bugs, and I think this requires some |
33 |
> discussion, hense this post. |
34 |
|
35 |
Please file a bug. |
36 |
|
37 |
> It'll take a couple of hours for another sync and update to run, |
38 |
> should I even bother with -r8? |
39 |
> |
40 |
> -JimC |
41 |
|
42 |
Don't bother because -r8 will behave the same way. |
43 |
|
44 |
Zac |
45 |
-----BEGIN PGP SIGNATURE----- |
46 |
Version: GnuPG v1.4.6 (GNU/Linux) |
47 |
|
48 |
iD8DBQFFiWaM/ejvha5XGaMRAgUgAJ41lhhIOaf9skhgl7PbKGdi0IlwOwCgv9+P |
49 |
rAG0JXBvX7m+25SPOZ5psr8= |
50 |
=nGqx |
51 |
-----END PGP SIGNATURE----- |
52 |
-- |
53 |
gentoo-portage-dev@g.o mailing list |