[gentoo-portage-dev] Masked by corruption

[James Cloos]

I'm getting an inordinate number of masked- by corruption failures
since merging portage-2.1.2_rc3-r7.

Part of the problem is the addition of the complete dep graph.  (Which
makes testing extraordinarily and horrifically painful; it now takes
emerge(1) about 20 to 30 minutes to get started, since reading in
everything in /var/db/pkg thrashes the dcache)  It is unable to
deal with some of the stuff already installed.

The corruption is not changed files.  Hashes of the ebuilds always
match the srings in the Manifest files.  It seems that it just doesn't
like old syntax.

Running with --debug did not explain what it found to be corrupt.

I don't see any relevant bugs, and I think this requires some
discussion, hense this post.

It'll take a couple of hours for another sync and update to run,
should I even bother with -r8?

-JimC
-- 
James Cloos [EMAIL PROTECTED] OpenPGP: 1024D/ED7DAEA6
-- 
gentoo-portage-dev@gentoo.org mailing list

Re: [gentoo-portage-dev] Masked by corruption

[Mike Auty]

Jim,
	I opened bug 158632, so that's worth looking at.  It also points to a 
post on the forums about the problem.  I can't add much to the 
discussion myself, just that it affected two of my machines differently 
which I found rather odd (one has difficulty with all versions of mpc, 
the other with only one version).  I hope that helps...

Mike  5:)
--
gentoo-portage-dev@gentoo.org mailing list

Re: [gentoo-portage-dev] Masked by corruption

[Zac Medico]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

James Cloos wrote:
 I'm getting an inordinate number of masked- by corruption failures
 since merging portage-2.1.2_rc3-r7.

Do you get a !!! Digest verification failed: message before that,
or only the masked by: corruption message?  Assuming that the
messages are invalid, you may be able to use FEATURES=-strict or
FEATURES=digest to avoid those messages.  However, you should know
exactly what those features do before you change them.

 Part of the problem is the addition of the complete dep graph.  (Which
 makes testing extraordinarily and horrifically painful; it now takes
 emerge(1) about 20 to 30 minutes to get started, since reading in
 everything in /var/db/pkg thrashes the dcache)  It is unable to
 deal with some of the stuff already installed.

It sounds like you're experiencing this bug:

https://bugs.gentoo.org/show_bug.cgi?id=158649

I'll get that one fixed ASAP.

 The corruption is not changed files.  Hashes of the ebuilds always
 match the srings in the Manifest files.  It seems that it just doesn't
 like old syntax.
 
 Running with --debug did not explain what it found to be corrupt.
 
 I don't see any relevant bugs, and I think this requires some
 discussion, hense this post.

Please file a bug.

 It'll take a couple of hours for another sync and update to run,
 should I even bother with -r8?
 
 -JimC

Don't bother because -r8 will behave the same way.

Zac
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFiWaM/ejvha5XGaMRAgUgAJ41lhhIOaf9skhgl7PbKGdi0IlwOwCgv9+P
rAG0JXBvX7m+25SPOZ5psr8=
=nGqx
-END PGP SIGNATURE-
-- 
gentoo-portage-dev@gentoo.org mailing list