From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: udev downgrade
Date: Fri, 4 Jan 2013 02:54:31 +0000 (UTC) [thread overview]
Message-ID: <loom.20130104T034050-613@post.gmane.org> (raw)
In-Reply-To: loom.20130103T202419-425@post.gmane.org
James <wireless <at> tampabay.rr.com> writes:
> So unless somebody can give me good reason, I'm downgrading to
> udev-171 asap on this (only) system running udev 196.......
> (ps, I like to experiment, but not with udev et. al.)
Long night, when you have to answer your own posts.....
Now I get:
emerge -p1u udev
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild UD ] sys-fs/udev-171-r9 [196-r1] USE="rule_generator%*
-action_modeswitch% -build% -debug% -edd% (-extras) -floppy% {-test%}"
[blocks B ] <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking
sys-fs/udev-init-scripts-17-r1)
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
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
(no parents that aren't satisfied by other packages in this slot)
ideas?
James
next prev parent reply other threads:[~2013-01-04 2:56 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 ` James [this message]
2013-01-04 3:09 ` [gentoo-user] " 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
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.20130104T034050-613@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