[gentoo-user] World update and dev-lang/python-exec weirdness...

[gentoo-user] World update and dev-lang/python-exec weirdness...

[Tanstaafl]

Ok, I don't understand this...

If I do an emerge -pvuDN world, it tells me I only need to update (among 
a few other things) ONE version of dev-lang/python-exec: (2.0.1 to -r1).

I then tried to selectively update just the kernel, and it complains 
about python-exec-2.0.1 being masked, so I add that to the emerge command:

emerge -pvuDN dev-lang/python-exec gentoo-sources

This results in no blockers, BUT, NOW it wants to update TWO versions of 
python-exec: dev-lang/python-exec 2.0.1 AND dev-lang/python-exec-0.3.1 
(to -r1).

First question is, why does a plain emerge -pvuDN world NOT want to 
update both of these?

Second questions is, do I even NEED both of these? Or can (or more 
importantly, SHOULD) I just emerge -C dev-lang/python-exec-0.3.1?

Thanks,

Charles

Re: [gentoo-user] World update and dev-lang/python-exec weirdness...

[Todd Goodman]

* Tanstaafl <tanstaafl@libertytrek.org> [140308 09:46]:
> Ok, I don't understand this...
> 
> If I do an emerge -pvuDN world, it tells me I only need to update (among 
> a few other things) ONE version of dev-lang/python-exec: (2.0.1 to -r1).
> 
> I then tried to selectively update just the kernel, and it complains 
> about python-exec-2.0.1 being masked, so I add that to the emerge command:
> 
> emerge -pvuDN dev-lang/python-exec gentoo-sources
> 
> This results in no blockers, BUT, NOW it wants to update TWO versions of 
> python-exec: dev-lang/python-exec 2.0.1 AND dev-lang/python-exec-0.3.1 
> (to -r1).
> 
> First question is, why does a plain emerge -pvuDN world NOT want to 
> update both of these?
> 
> Second questions is, do I even NEED both of these? Or can (or more 
> importantly, SHOULD) I just emerge -C dev-lang/python-exec-0.3.1?
> 
> Thanks,
> 
> Charles

Hi Charles,

dev-lang/python-exec is slotted (I have slot 0 and 2 on my system.)

I assume when you do the emerge -pvuDN world it only tells you about
slot 2 because there's only a dependency on slot 2.  When you ask it to
emerge dev-lang/python-exec it tries to emerge for all slots (I'm not
sure, someone please correct me if that's not what's happening.)

But I had a problem where something using python-exec needed to be
rebuilt.  Run an emerge -pvutDN world (add the -t option to see the tree
of dependencies) and look for what wants the masked python-exec.  Then
rebuild that manually.

I'm running ~x86 btw.

Regards,

Todd

Re: [gentoo-user] World update and dev-lang/python-exec weirdness...

[Tanstaafl]

On 3/8/2014 10:12 AM, Todd Goodman <tsg@bonedaddy.net> wrote:
> * Tanstaafl <tanstaafl@libertytrek.org> [140308 09:46]:
>> If I do an emerge -pvuDN world, it tells me I only need to update (among
>> a few other things) ONE version of dev-lang/python-exec: (2.0.1 to -r1).
>>
>> I then tried to selectively update just the kernel, and it complains
>> about python-exec-2.0.1 being masked, so I add that to the emerge command:
>>
>> emerge -pvuDN dev-lang/python-exec gentoo-sources
>>
>> This results in no blockers, BUT, NOW it wants to update TWO versions of
>> python-exec: dev-lang/python-exec 2.0.1 AND dev-lang/python-exec-0.3.1
>> (to -r1).
>>
>> First question is, why does a plain emerge -pvuDN world NOT want to
>> update both of these?
>>
>> Second questions is, do I even NEED both of these? Or can (or more
>> importantly, SHOULD) I just emerge -C dev-lang/python-exec-0.3.1?

> dev-lang/python-exec is slotted (I have slot 0 and 2 on my system.)
>
> I assume when you do the emerge -pvuDN world it only tells you about
> slot 2 because there's only a dependency on slot 2.  When you ask it to
> emerge dev-lang/python-exec it tries to emerge for all slots (I'm not
> sure, someone please correct me if that's not what's happening.)
>
> But I had a problem where something using python-exec needed to be
> rebuilt.  Run an emerge -pvutDN world (add the -t option to see the tree
> of dependencies) and look for what wants the masked python-exec.  Then
> rebuild that manually.

Thanks... so, since it is slotted, I guess my question about needing 
them both is, yes, I need them both (ie, don't emerge -C the older 0.3.1 
version)...

[gentoo-user] Re: World update and dev-lang/python-exec weirdness...

[Jonathan Callen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 03/08/2014 11:24 AM, Tanstaafl wrote:
> On 3/8/2014 10:12 AM, Todd Goodman <tsg@bonedaddy.net> wrote:
>> * Tanstaafl <tanstaafl@libertytrek.org> [140308 09:46]:
>>> If I do an emerge -pvuDN world, it tells me I only need to update (among a few other
>>> things) ONE version of dev-lang/python-exec: (2.0.1 to -r1).
>>> 
>>> I then tried to selectively update just the kernel, and it complains about
>>> python-exec-2.0.1 being masked, so I add that to the emerge command:
>>> 
>>> emerge -pvuDN dev-lang/python-exec gentoo-sources
>>> 
>>> This results in no blockers, BUT, NOW it wants to update TWO versions of python-exec:
>>> dev-lang/python-exec 2.0.1 AND dev-lang/python-exec-0.3.1 (to -r1).
>>> 
>>> First question is, why does a plain emerge -pvuDN world NOT want to update both of these?
>>> 
>>> Second questions is, do I even NEED both of these? Or can (or more importantly, SHOULD) I
>>> just emerge -C dev-lang/python-exec-0.3.1?
> 
>> dev-lang/python-exec is slotted (I have slot 0 and 2 on my system.)
>> 
>> I assume when you do the emerge -pvuDN world it only tells you about slot 2 because there's
>> only a dependency on slot 2.  When you ask it to emerge dev-lang/python-exec it tries to
>> emerge for all slots (I'm not sure, someone please correct me if that's not what's
>> happening.)
>> 
>> But I had a problem where something using python-exec needed to be rebuilt.  Run an emerge
>> -pvutDN world (add the -t option to see the tree of dependencies) and look for what wants the
>> masked python-exec.  Then rebuild that manually.
> 
> Thanks... so, since it is slotted, I guess my question about needing them both is, yes, I need
> them both (ie, don't emerge -C the older 0.3.1 version)...
> 
> 

You really shouldn't ever `emerge -C` anything, instead using `emerge -c`, which will refuse to
remove anything that might break the system in the course of its removal (due to dependencies).
In fact, if you want to see what you have that is keeping a particular package on the system, you
can do `emerge -pvc the/package`, which will list the reasons why the package cannot be removed.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCgAGBQJTG2p3AAoJELHSF2kinlg445wP/0P8ji5HLOR1WOeSfjnOzhgF
1hjkjL7ciJrQkxWX6F4ZW/7b4VfiqCJM0RiKNZLlFyBjsINfnKZxGUHfm9ISE31p
4DbW8idMaf5RYETd4I1PFkhdDL1PptWFIK/2lkIWu38LwtbtBkgJqv/RbkayE72q
lEkCKJgYRukiwsLbdkDc0LhLjcmbW6uteWvweClPxPPekvP3arFNiJBcoOoBFeA6
KQIli6GQlEEhs/Hf9tV4NA6tiikCI8al1/FWsqmOcoslpgaQBmTlbIKjRE6WYlVb
tW59wLQskIcPJ6HQ3vscqu86m0DFPSvu1RbKYNK8dK20fW8AMjIl3cV/rsXsSPKr
VphKCfyw4aD5ik9blVwTV3JHu4klh8z1V0w/UVJzt6pZmh7N5sXYdXmGys3wsJxd
tyiwmxRi4k5OUAWq8e8ajVBzyJS4t4N9BFlBm2U+I2JYLytm1fszAwZrtRKmUAue
0Nd7dVEibuL7aVrXDQa4ztT5v/WMHP+gMeP3eKdDfkT2XBvPx+4C1A2An5eKaAHg
zOJu6HjzFB56qajAoDqlcSOlkUJakW5xaluI+56MFWVEmmIx/ExX+UlNBmM+nAfm
OfYCZ5DILphw69wJ0UfFwdVQHVr55WIJfr3tPEUC72u/RcGLvUQ8dFaqI37MhKn/
EUviJlPtENyeqGwX+EVZ
=Scbb
-----END PGP SIGNATURE-----

Re: [gentoo-user] World update and dev-lang/python-exec weirdness...

[Tom Wijsman]

On Sat, 8 Mar 2014 10:12:13 -0500
Todd Goodman <tsg@bonedaddy.net> wrote:

> When you ask it to emerge dev-lang/python-exec it tries to emerge for
> all slots (I'm not sure, someone please correct me if that's not
> what's happening.)

Consider what happened when you did `sys-kernel/gentoo-sources` in the
installation; it is a slotted package, it only brings in the latest
visible version.

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D