[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    [gentoo-dev] another snag:  emerge -Up --deep gtkhtml
From:       Denys Duchier <duchier () ps ! uni-sb ! de>
Date:       2003-04-30 14:37:27
[Download RAW message or body]

I hope my continued reports on "emerge -U" are neither out of place
nor too tiresome.  Today, I "emerge sync"'d, tried "emerge -Up --deep
world" and got the following error:


% emerge -Up --deep world
>>> --upgradeonly implies --update... adding --update to options.

These are the packages that I would merge, in order:

Calculating world dependencies \
!!! all ebuilds that could satisfy "=gnome-extra/gal-0.24*" have been masked.
!!!    (dependency required by "gnome-extra/gtkhtml-1.1.10" [ebuild])

!!! Problem with ebuild gnome-extra/gtkhtml-1.1.10
!!! Possibly a DEPEND/*DEPEND problem.

!!! Depgraph creation failed.


Then I checked more specifically with:


% emerge -Up --deep gtkhtml
>>> --upgradeonly implies --update... adding --update to options.

These are the packages that I would merge, in order:

Calculating dependencies \
!!! all ebuilds that could satisfy "=gnome-extra/gal-0.24*" have been masked.
!!!    (dependency required by "gnome-extra/gtkhtml-1.1.10" [ebuild])

!!! Error calculating dependancies. Please correct.


Then I tried:


% ACCEPT_KEYWORDS="~x86" emerge -Up --deep gtkhtml


and this worked fine and printed a list in which NEITHER gal nor
gtkhtml appeared.


My guess is that "emerge -U --deep" is not prepared to investigate
~arch masked dependencies eventhough their are (obviously) installed.

Again it seems to me that this violates the intended purpose of -U
which is to conveniently upgrade a Gentoo installation where some
masked packages may have been installed.

Is the current behaviour a design decision or a "not implemented yet"
corner case of emerge?

Cheers,

-- 
Dr. Denys Duchier
Équipe Calligramme
LORIA, Nancy, FRANCE

--
gentoo-dev@gentoo.org mailing list


[prev in list] [next in list] [prev in thread] [next in thread]