From: Bruce Hill <daddy@happypenguincomputers.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] I'm confused by "[ebuild U #] virtual/udev-197 [171]". Help, please!
Date: Sun, 20 Jan 2013 16:21:15 -0600 [thread overview]
Message-ID: <20130120222115.GD2507@server> (raw)
In-Reply-To: <20130120205012.GB3091@acm.acm>
On Sun, Jan 20, 2013 at 08:50:12PM +0000, Alan Mackenzie wrote:
> Hi, Gentoo!
>
> After synching, I've got a whole lot of programs to emerge, amongst them
> being udev-197. :-( I'd rather do this on its own, in peace and quiet,
> rather than together with 12 or 13 other programs.
>
> emerge -puND world generates these:
>
> [ebuild U #] sys-fs/udev-197-r4 [171-r9] USE="acl%* kmod%* openrc%* -doc% -static-libs%"
> [ebuild U #] virtual/udev-197 [171]
>
> . The # indicates the packages are masked in packages.mask, which
> indeed they are. The emerge man-page indicates that these new versions
> will nevertheless be merged. But surely this is what the entry in
> packages.mask is to prevent? Why does emerge want to merge udev-197 in
> this case? How do I stop it?
>
> What am I missing here?
I ran across this new virtual/udev problem today, also. Issuing "eix
virtual/udev" told me it's a "Virtual to select between sys-fs/udev and
sys-fs/eudev". Since it's not my intention atm to upgrade udev to >= 181, or
install eudev, I added ">=virtual/udev-181" and now my working Gentoo system
no longer wants to upgrade udev.
--
Happy Penguin Computers >')
126 Fenco Drive ( \
Tupelo, MS 38801 ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/
Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
prev parent reply other threads:[~2013-01-20 22:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 20:50 [gentoo-user] I'm confused by "[ebuild U #] virtual/udev-197 [171]". Help, please! Alan Mackenzie
2013-01-20 21:18 ` Alan McKinnon
2013-01-20 22:22 ` Alan Mackenzie
2013-01-21 0:27 ` Dale
2013-01-21 0:37 ` Dale
2013-01-21 6:00 ` Walter Dnes
2013-01-20 22:21 ` Bruce Hill [this message]
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=20130120222115.GD2507@server \
--to=daddy@happypenguincomputers.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