| 1 |
On Tue, 27 Dec 2005 17:52:16 -0800 |
| 2 |
Zac Medico <zmedico@×××××.com> wrote: |
| 3 |
|
| 4 |
|
| 5 |
> http://bugs.gentoo.org/show_bug.cgi?id=115593 |
| 6 |
> |
| 7 |
> That's with portage-2.0.53, right? |
| 8 |
> |
| 9 |
> Zac |
| 10 |
|
| 11 |
Yes, that's it. From the bug, it seems the problems are in the ebuilds. However, the |
| 12 |
updated portage's solution is to remove them from the world file. Thus a loop |
| 13 |
gets created - |
| 14 |
|
| 15 |
emaint --fix world removes the packages) |
| 16 |
regenworld adds the packages back in. |
| 17 |
emerge -uDNav world generatea the error - |
| 18 |
Problems have been detected with your world file |
| 19 |
Please run emaint --check world |
| 20 |
|
| 21 |
While there are problems, though I'm not sure what exactly they are, the new |
| 22 |
portage notes them. Then puts itself in a, slow, loop with some hope someone |
| 23 |
else knows how to fix the problems. |
| 24 |
|
| 25 |
The problem portage thinks that exists seems to be with some allowed keywords and |
| 26 |
masked packages, not as it reports - no ebuilds available. Though, it could be technically |
| 27 |
argued that using "x86", "~x86", and "-*" in /usr/etc/portage.keywords, on my system |
| 28 |
is incorrect. It is somewhat misleading to say - no ebuilds available, implying that no |
| 29 |
ebuilds with the arch keyword of the running system is available. |
| 30 |
|
| 31 |
Bob |
| 32 |
- |
| 33 |
-- |
| 34 |
gentoo-user@g.o mailing list |
Archives