public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Burak Arslan <burak.arslan@arskom.com.tr>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] make catalyst call emerge --deep
Date: Wed, 10 Apr 2013 18:54:47 +0300	[thread overview]
Message-ID: <51658B47.3020008@arskom.com.tr> (raw)

Hi,

In a build (a desktop stage 4) I'm trying to run, I'm getting multiple 
udevs (=197-r1 and >=197-r2) pulled in (among other errors, see below). 
My impression is that if I were able to pass --deep to emerge command, 
it'd just go through. Is there a non-hacky way of doing this?

Best regards,
Burak

======================

[blocks B     ] <sys-apps/sandbox-2.6-r1 ("<sys-apps/sandbox-2.6-r1" is 
blocking dev-lang/python-3.3.0-r1)

!!! 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-197-r1::gentoo, installed) pulled in by
     =virtual/udev-197-r1 required by (virtual/dev-manager-0::gentoo, 
installed)
     (and 18 more with the same problem)

   (virtual/udev-197-r2::gentoo, ebuild scheduled for merge) pulled in by
     >=virtual/udev-197[gudev,hwdb] required by 
(sys-fs/udisks-2.1.0::gentoo, ebuild scheduled for merge)
     >=virtual/udev-197[gudev] required by 
(sys-power/upower-0.9.20-r2::gentoo, ebuild scheduled for merge)




             reply	other threads:[~2013-04-10 15:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10 15:54 Burak Arslan [this message]
2013-04-10 16:16 ` [gentoo-catalyst] Re: make catalyst call emerge --deep W. Trevor King
2013-04-10 16:22 ` [gentoo-catalyst] " Rick "Zero_Chaos" Farina
2013-04-10 17:35 ` Matt Turner
2013-04-10 19:41   ` Rick "Zero_Chaos" Farina
2013-04-11  4:42 ` Peter Stuge

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=51658B47.3020008@arskom.com.tr \
    --to=burak.arslan@arskom.com.tr \
    --cc=gentoo-catalyst@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