[gentoo-catalyst] make catalyst call emerge --deep

[gentoo-catalyst] make catalyst call emerge --deep

[Burak Arslan]

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)

[gentoo-catalyst] Re: make catalyst call emerge --deep

[W. Trevor King]

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

On Wed, Apr 10, 2013 at 06:54:47PM +0300, Burak Arslan wrote:
> 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?

Are you using `update_seed: yes` in your stage1 spec?  You may also
need to set update_seed_comman, since by default catalyst only updates
gcc and its dependencies.  Seed updates are not super clear to me, and
there has been a good deal of talk about seed updates on the list
recently [1,2,3], so take my advice with a grain of salt ;).

Cheers,
Trevor

[1]: http://thread.gmane.org/gmane.linux.gentoo.catalyst/2137
[2]: http://thread.gmane.org/gmane.linux.gentoo.catalyst/2166
[3]: http://thread.gmane.org/gmane.linux.gentoo.catalyst/2209

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [gentoo-catalyst] make catalyst call emerge --deep

[Rick "Zero_Chaos" Farina]

-----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-----

Re: [gentoo-catalyst] make catalyst call emerge --deep

[Matt Turner]

On Wed, Apr 10, 2013 at 8:54 AM, Burak Arslan
<burak.arslan@arskom.com.tr> 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?

Modify catalyst and try it. We should confirm that --deep actually
would fix this problem before deciding it's the solution.

If it is, I'm all for adding it.

Re: [gentoo-catalyst] make catalyst call emerge --deep

[Rick "Zero_Chaos" Farina]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/10/2013 01:35 PM, Matt Turner wrote:
> On Wed, Apr 10, 2013 at 8:54 AM, Burak Arslan
> <burak.arslan@arskom.com.tr> 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?
> 
> Modify catalyst and try it. We should confirm that --deep actually
> would fix this problem before deciding it's the solution.

I have no idea, I've never hit this problem as --deep is in my profile
as a default option.
> 
> If it is, I'm all for adding it.
> 
> 

- -ZC
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRZcBTAAoJEKXdFCfdEflK6M4P/0EQUdBTbTkFb6nIaM0YPYkP
a0oQgIlr/xOtMdC8L5AKka33I2MZx1Ums7WtwbAj1lbxtfy/fp4MKognnUFeBsOq
aNNa2JcfvN6n3mN9spfb5mZ1blPCZyhBBaFsNoCdNroY54Bt/YhBkKSMMIvp5l2h
bqYD3ibkXBhuYrYZqdNW9zxIIhKT9OOEMo8VBLXXQCoo1YAsXiv6oHi2A7xQshRb
4ggV3EqSBQfeS3yAH1+VlRPR+zXTaOrEkO5QssDa5PZ4T8WALlaattOaR0mrDYm/
bRsQPaYWGGwKLuDh3vKe54CYUreNR5UkuqqlEpZNdfd36m4lzqIbcDynu1iTCf1L
AmYuyP/Vyn+cNFhfEU06OlOu7iVdSa1v7QQDLhHbg7LzD4u7fIAwPEy8q5UqFbV0
qs2cSgplzsiCYiaoAkZGsqbXKXYo3UIKGIcXP+l4UhCXLJoOj3nxThshyv/IR85I
f2kASNkMXoZui5AAcXWR4rPpO4LwtdtyDKxaF1YlFCgN5Y+AxaZLYCOlIj54VYs0
F6KfFwRGPZnHN91DGm8xWvKYeLW+YAGVR9Z0mobXihL/PpQpiwboO9kvIfxAPLdv
VdVjd3KZD1hcqSZ5pcxWnToTgZfJ06VVWXkUsX1B45OoUFswh8NO1QnMGlNXflDA
Qf5WYHLkFXPwoWHTCi5c
=WbJw
-----END PGP SIGNATURE-----

Re: [gentoo-catalyst] make catalyst call emerge --deep

[Peter Stuge]

Burak Arslan wrote:
> Is there a non-hacky way of doing this?

You can include emerge options in stage4/packages in the spec file.


//Peter