On 10/3/06, Bo Ørsted Andresen [EMAIL PROTECTED] wrote:
On Tuesday 03 October 2006 22:14, Justin Patrin wrote:
I'm getting this very odd behavior when trying to --update --deep world.
# emerge -atuDv world
These are the packages that would be merged, in reverse order:
Calculating world dependencies... done!
[blocks B ] =app-admin/eselect-1.0.3 (is blocking
app-admin/eselect-opengl-1.0.3)
[nomerge ] x11-terms/xterm-218 USE=truetype -Xaw3d -paste64
-toolbar -unicode
[nomerge ] sys-libs/libutempter-1.1.4.1
[nomerge ] app-arch/rpm2targz-9.0-r3
[nomerge ]sys-apps/util-linux-2.12r-r4 USE=crypt nls perl
-old-crypt (-selinux) -static
[nomerge ] app-crypt/hashalot-0.3-r2
[ebuild N] app-admin/eselect-opengl-1.0.3 41 kB
If I'm reading this right, xterm is deeply depending on eselect-opengl
somehow but eselect is blocking it. Does anyone know why this would
be?
app-admin/eselect-opengl-1.0.3 contains this:
RDEPEND==app-admin/eselect-1.0_rc1
!=app-admin/eselect-1.0.3
This means that it requires eselect = 1.0_rc1 but is blocked by eselect =
1.0.3. eselect-1.0.3 was marked testing and eselect-opengl-1.0.3 is marked
stable. So either downgrade eselect to latest stable (1.0.2) or upgrade
eselect-opengl to latest testing (1.0.4).
I am a bit curious about how eselect-opengl is being pulled in so if you still
see the above output feel free to add --debug to the above command and mail
the output to me offlist. If you do that be sure to include the output of
`emerge --info` also.
Ok, I figured out what was causing this.. I had eselect and
eselect-php in package.keywords (without any keywords) but not
eselect-opengl. This made eselect upgrade to 1.0.6 which didn't work
with eselect-opengl-1.0.3. Removing the eselect atoms from
package.keywords fixed the problem (eselect-1.0.2 and
eselect-opengl-1.0.3).
(I think I added these packages to package.keywords because of a
previous PHP upgrade. It appears that eselect-php doesn't exist any
more, though.)
All is now well. Thanks.
--
Justin Patrin
--
gentoo-user@gentoo.org mailing list
