emerge rsync; emerge -up world

l8nite · n00b Joined: 16 Jun 2002 Posts: 58 Location: Sunnyvale, Ca

I've been running the subject commands on two completely different machines for the past 3 days, and emerge fails each time with the following error:

dellb0x l8nite # emerge -up world
These are the packages that I would merge, in order.
Calculating world dependencies |
emerge: all ebuilds that could satisfy ">=gnome-base/gnome-panel-2.0.11" (from ebuild / gnome-base/gnome-2.0.3 merge) have been masked.

I tried removing /usr/portage/* and resyncing, but to no avail.

Anyone else having the same problem or know of a fix?

sa · Guru Joined: 10 Jun 2002 Posts: 450

you could try:

emerge /usr/portage/gnome-base/gnome-panel/gnome-panel-2.0.11.ebuild

but mabey look in /usr/portage/profiles/package.mask to see wh it is masked first.

l8nite · n00b Joined: 16 Jun 2002 Posts: 58 Location: Sunnyvale, Ca

I emerged gnome-panel-2.0.11 as you suggested, but it didn't fix the problem with emerge -up failing.

Checking /usr/portage/profiles/package.mask reveals >=gnome-base/gnome-panel-2.1

I'm stumped :cry:

l8nite

sa · Guru Joined: 10 Jun 2002 Posts: 450

is the `emerge -up world` error still the same after you emerge the updated gnome panel?

darktux · Posted: Thu Dec 05, 2002 10:42 pm Post subject:

Try now! I believe your problem is gone

_________________
Lego my ego, and I'll lego your knowledge

www.tuxslare.org - My reborn website

l8nite · n00b Joined: 16 Jun 2002 Posts: 58 Location: Sunnyvale, Ca

Hi, thanks for the input so far - I've tried several times this morning again and it's still giving me the same error:

pascall · Posted: Fri Dec 06, 2002 7:38 pm Post subject:

Hey l8nite,

I have exactly the same problem. I filed a bug report (follow https://bugs.gentoo.org/show_bug.cgi?id=11603). Problem is very strange cause when I 'touch' the ebuild file, problem goes to another file. I don t how where it comes from.

Could it be related to the keywords ? I accept x86 but not ~x86, and the packages posing problem have all the x86 keywords.

pascall · Posted: Sat Dec 07, 2002 1:11 am Post subject:

Problem solved : I upped portage to 2.0.45-r1 and problem disappeared....

Hope it ll works for other too

l8nite · n00b Joined: 16 Jun 2002 Posts: 58 Location: Sunnyvale, Ca

Thanks for the tip - Very odd behavior though :roll:

l8nite