From: "Rick \"Zero_Chaos\" Farina" <zerochaos@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] make catalyst call emerge --deep
Date: Wed, 10 Apr 2013 12:22:15 -0400 [thread overview]
Message-ID: <516591B7.90702@gentoo.org> (raw)
In-Reply-To: <51658B47.3020008@arskom.com.tr>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/10/2013 11:54 AM, Burak Arslan wrote:
> 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?
Personally I use /etc/catalyst/catalystrc for this kind of thing. I do
it like this:
export EMERGE_DEFAULT_OPTS="$(portageq envvar EMERGE_DEFAULT_OPTS)
- --jobs=48 --with-bdeps=y --deep --whatever-else-you-want"
Honestly I'm all for changing catalyst to ALWAYS use --deep and just
making it part of the default options. I really don't see it slowing
dep calculation down enough to be a major negative and I only see it
helping.
Anyone from the team care to weigh in on it?
- -Zero
>
> 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)
>
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRZZG3AAoJEKXdFCfdEflK+X8QAIIAfElC71/ilrmrm5+fEm3o
YVr0bT5MRuL9SY8jVEZItDIhRLyvnt+2CSu4kEyV5xR/7Wss31DkbaMg8DuO7ieF
jvDYRMgQK4veNHaEzGNZhTaEBSNY/UFLv8Hd3np/viQnC8U9vl+vycaa8w4Psv6v
pZPvPA4WQrYzmXb5Yc85PDT+AINQHuthfvuDakaDizXP6/GMFBb2/KAjr+NFV8US
hOhQw0mjRb8f/wZRSNQKW29EECKcs0E1jVSu3SoVFxZqYOGSHF5bkBL4nliMY7Uc
OVKFUGfhpf98XX8iYFwtwqQEC53CTooUVisx/RyHydmGNlBZXEJYDxIp8BxKiH7m
oBKTzOR0WmbkjXlKzaO/mXF3LLBEBqZ8hwvx8cOegI2blQjOuiO0UKe+qeVWl6hQ
MgonSXulIi1Oq3bciL6JSp4O2MPkREu3ukjYVp9fuGYRnC6JGt7GvzQhykYdU9wH
leYADAPkCG3hdpLJLAiHA7uDdiLbLbFJqdP49+alIML0B4CidmrO0TmLVF6kGHmT
HfvcdreV6TV8GOlK5YFtWsj7JLvp3Jvo49X21DAKIO7Gd46qwR9biGpVluLGPP8B
+aJ8eEY3wPIMUV1Wq6s7/IVP4coB4SSJxV135pvvqT83FpXX+GQJEwVGXyhdAF0e
7wa+9Gb5e7I2aDghyKGi
=0Ohe
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-04-10 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 15:54 [gentoo-catalyst] make catalyst call emerge --deep Burak Arslan
2013-04-10 16:16 ` [gentoo-catalyst] " W. Trevor King
2013-04-10 16:22 ` Rick "Zero_Chaos" Farina [this message]
2013-04-10 17:35 ` [gentoo-catalyst] " 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=516591B7.90702@gentoo.org \
--to=zerochaos@gentoo.org \
--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