From: "Stefan G. Weichinger" <lists@xunil.at>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: trouble understanding a slot conflict
Date: Tue, 03 Apr 2012 10:59:22 +0200 [thread overview]
Message-ID: <4F7ABBEA.50202@xunil.at> (raw)
In-Reply-To: <20120403085342.4acca18f@digimed.co.uk>
Am 03.04.2012 09:53, schrieb Neil Bothwick:
> Yes. What has happened is that the ID data has been moved out of
> pciutils and usbutils, so hwids blocks the older versions. If you
> want to stick with the older udev, you need the older pciutils and
> this means you need a matching version of usbutils. All this will
> disappear when you unmask udev, as it did for me yesterday.
It didn't for me.
I did:
emerge -C usbutils
emerge -C pciutils
emerge hwids
emerge usbutils pciutils
Not the most elegant approach, sure.
next prev parent reply other threads:[~2012-04-03 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 2:20 [gentoo-user] trouble understanding a slot conflict Allan Gottlieb
2012-04-03 2:07 ` [gentoo-user] " walt
2012-04-03 3:13 ` Allan Gottlieb
2012-04-03 7:53 ` Neil Bothwick
2012-04-03 8:59 ` Stefan G. Weichinger [this message]
2012-04-03 9:37 ` Neil Bothwick
2012-04-03 13:17 ` Allan Gottlieb
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=4F7ABBEA.50202@xunil.at \
--to=lists@xunil.at \
--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