From: Dan Johansson <Dan.Johansson@dmj.nu>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] update world with emul-linux-x86 blocks
Date: Sat, 3 Sep 2011 11:17:19 +0200 [thread overview]
Message-ID: <201109031117.20032.Dan.Johansson@dmj.nu> (raw)
Since some time I am getting the following errors while doing update world on
my dektop machine (running amd64 stable):
-------------------------------------8<------------------------------------
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] app-emulation/emul-linux-x86-baselibs-20110722 [20110129]
USE="-development" 34,381 kB
[ebuild U ] app-emulation/emul-linux-x86-opengl-20110722 [20110129-r1]
USE="-development" 44,036 kB
[ebuild U ] app-emulation/emul-linux-x86-xlibs-20110722 [20110129]
USE="opengl -development" 2,586 kB
[ebuild U ] app-emulation/emul-linux-x86-gtklibs-20110722 [20110129]
USE="-development" 4,714 kB
[ebuild U ] app-emulation/emul-linux-x86-medialibs-20110722 [20110129]
USE="-development" 7,874 kB
[ebuild U ] app-emulation/emul-linux-x86-soundlibs-20110722 [20110129]
USE="alsa -development -pulseaudio" 5,966 kB
[ebuild U ] app-emulation/emul-linux-x86-qtlibs-20110722 [20110129]
USE="-development" 16,626 kB
Total: 7 packages (7 upgrades), Size of downloads: 116,180 kB
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
app-emulation/emul-linux-x86-xlibs:0
(app-emulation/emul-linux-x86-xlibs-20110129::gentoo, installed) pulled in
by
~app-emulation/emul-linux-x86-xlibs-20110129 required by (app-
emulation/emul-linux-x86-motif-20110129::gentoo, installed)
(app-emulation/emul-linux-x86-xlibs-20110722::gentoo, ebuild scheduled for
merge) pulled in by
~app-emulation/emul-linux-x86-xlibs-20110722 required by (app-
emulation/emul-linux-x86-medialibs-20110722::gentoo, ebuild scheduled for
merge)
(and 2 more with the same problem)
app-emulation/emul-linux-x86-baselibs:0
(app-emulation/emul-linux-x86-baselibs-20110722::gentoo, ebuild scheduled
for merge) pulled in by
~app-emulation/emul-linux-x86-baselibs-20110722 required by (app-
emulation/emul-linux-x86-xlibs-20110722::gentoo, ebuild scheduled for merge)
(and 4 more with the same problem)
(app-emulation/emul-linux-x86-baselibs-20110129::gentoo, installed) pulled
in by
~app-emulation/emul-linux-x86-baselibs-20110129 required by (app-
emulation/emul-linux-x86-xlibs-20110129::gentoo, installed)
-------------------------------------8<------------------------------------
What would be the correct way to resolve this issue?
I am a little bit afraid to start unmerging any of these packages as among
other things sys-boot/grub depends on some of them.
Regards,
--
Dan Johansson, <http://www.dmj.nu>
***************************************************
This message is printed on 100% recycled electrons!
***************************************************
next reply other threads:[~2011-09-03 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-03 9:17 Dan Johansson [this message]
2011-09-03 10:31 ` [gentoo-user] update world with emul-linux-x86 blocks Mick
2011-09-03 11:16 ` Dan Johansson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201109031117.20032.Dan.Johansson@dmj.nu \
--to=dan.johansson@dmj.nu \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox