On (27/12/05 21:51), Bob Sanders wrote: > On Tue, 27 Dec 2005 17:52:16 -0800 > Zac Medico <[EMAIL PROTECTED]> wrote: > > > > http://bugs.gentoo.org/show_bug.cgi?id=115593 > > > > That's with portage-2.0.53, right? > > > > Zac > > Yes, that's it. From the bug, it seems the problems are in the ebuilds. > However, the > updated portage's solution is to remove them from the world file. Thus a loop > gets created - > > emaint --fix world removes the packages) > regenworld adds the packages back in. > emerge -uDNav world generatea the error - > Problems have been detected with your world file > Please run emaint --check world > > While there are problems, though I'm not sure what exactly they are, the new > portage notes them. Then puts itself in a, slow, loop with some hope someone > else knows how to fix the problems. > > The problem portage thinks that exists seems to be with some allowed keywords > and > masked packages, not as it reports - no ebuilds available. Though, it could > be technically > argued that using "x86", "~x86", and "-*" in /usr/etc/portage.keywords, on my > system > is incorrect. It is somewhat misleading to say - no ebuilds available, > implying that no > ebuilds with the arch keyword of the running system is available. > > Bob > - > -- > gentoo-user@gentoo.org mailing list > Hi, Same problem here, nothing usefull in Bug-115593 (at least for me). Latest portage-2.1-pre2. All ~x86 system. Rumen
pgpajxCp5FBtY.pgp
Description: PGP signature
