public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: trouble understanding a slot conflict
Date: Tue, 3 Apr 2012 08:53:42 +0100	[thread overview]
Message-ID: <20120403085342.4acca18f@digimed.co.uk> (raw)
In-Reply-To: <yu9vclhcxso.fsf@nyu.edu>

[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]

On Mon, 02 Apr 2012 23:13:43 -0400, Allan Gottlieb wrote:

> Yes indeed I have it masked for exactly that reason.  I will be going to
> a combined / + /usr when the semester ends.  I use this machine for my
> lectures and assignments so prefer to break it from late may through
> august.
> 
> I just tried masking the -r2 (and higher) pciutils.
> But this conflicts with a newly-required hwids-2012-0401.
> The later is required by a new usbutils-005-r1
> 
> This led me to mask >=usbutils-005-r1.
> 
> Now the proposed update world leaves portage happy, but me worried.  I
> haven't actually done the update world.  It is reasonably to have so
> much masking? 

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.
 

-- 
Neil Bothwick

"Good Enough" is the death knell of progress.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-04-03  7:55 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 [this message]
2012-04-03  8:59       ` Stefan G. Weichinger
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=20120403085342.4acca18f@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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