From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: udev downgrade
Date: Fri, 4 Jan 2013 16:23:14 +0000 (UTC) [thread overview]
Message-ID: <loom.20130104T171959-655@post.gmane.org> (raw)
In-Reply-To: 50E6745D.5020509@gmail.com
Dustin C. Hatch <admiralnemo <at> gmail.com> writes:
> The problem is you are trying to downgrade sys-fs/udev but not
> virtual/udev. If you want to force using udev-171, you need to mask both
> the real and virtual atoms. Try this in /etc/portage/package.mask/udev:
> >=sys-fs/udev-181
> >=virtual/udev-181
> Then emerge -avuD1 udev and see if that fixes it.
I get the downgrades you would expect:
UD ] virtual/udev-171 [196]
UD ] sys-fs/udev-171-r9
I also get some weird companion downgrades:
blocks B ] >x11-libs/qt-script-4.8.2-r9999:4
(">x11-libs/qt-script-4.8.2-r9999:4" is blocking x11-libs/qt-declarative-4.8.2,
x11-libs/qt-webkit-4.8.2, x11-libs/qt-svg-4.8.2, x11-libs/qt-test-4.8.2,
x11-libs/qt-xmlpatterns-4.8.2, x11-libs/qt-multimedia-4.8.2,
x11-libs/qt-opengl-4.8.2)
[blocks B ] <x11-libs/qt-gui-4.8.4:4
<snip>
and these:
Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
virtual/udev:0
(virtual/udev-171::gentoo,ebuild scheduled for merge) pulled in by
<virtual/udev-196 required by (sys-fs/lvm2-2.02.88::gentoo, installed)
=virtual/udev-171 required by (kde-base/kdelibs-4.9.3::gentoo, installed)
(and 17 more with the same problems)
(virtual/udev-196::gentoo, installed) pulled in by
>=virtual/udev-180 required by (sys-fs/udev-196-r1::gentoo, installed)
(and 1 more with the same problem)
sys-fs/udev:0
(sys-fs/udev-196-r1::gentoo, installed) pulled in by
>=sys-fs/udev-196-r1[gudev?,hwdb?,introspection?,keymap?,selinux?,static-libs?]
required by (virtual/udev-196::gentoo, installed)
(sys-fs/udev-171-r9::gentoo, ebuild scheduled for merge) pulled in by
~sys-fs/udev-171[gudev?,hwdb?,introspection?,keymap?,selinux?] required by
(virtual/udev-171::gentoo, ebuild scheduled for merge)
<snip>
Does this look normal?
James
next prev parent reply other threads:[~2013-01-04 16:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 19:34 [gentoo-user] udev downgrade James
2013-01-04 2:54 ` [gentoo-user] " James
2013-01-04 3:09 ` Bruce Hill
2013-01-04 9:16 ` Matthias Hanft
2013-01-04 6:19 ` Dustin C. Hatch
2013-01-04 11:44 ` Bruce Hill
2013-01-04 16:23 ` James [this message]
2013-01-04 17:28 ` Mark Knecht
2013-01-04 19:52 ` Dustin C. Hatch
2013-01-04 20:31 ` Kevin Chadwick
2013-01-04 20:17 ` Dustin C. Hatch
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=loom.20130104T171959-655@post.gmane.org \
--to=wireless@tampabay.rr.com \
--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