| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA512 |
| 3 |
|
| 4 |
On 03/08/2014 11:24 AM, Tanstaafl wrote: |
| 5 |
> On 3/8/2014 10:12 AM, Todd Goodman <tsg@×××××××××.net> wrote: |
| 6 |
>> * Tanstaafl <tanstaafl@×××××××××××.org> [140308 09:46]: |
| 7 |
>>> If I do an emerge -pvuDN world, it tells me I only need to update (among a few other |
| 8 |
>>> things) ONE version of dev-lang/python-exec: (2.0.1 to -r1). |
| 9 |
>>> |
| 10 |
>>> I then tried to selectively update just the kernel, and it complains about |
| 11 |
>>> python-exec-2.0.1 being masked, so I add that to the emerge command: |
| 12 |
>>> |
| 13 |
>>> emerge -pvuDN dev-lang/python-exec gentoo-sources |
| 14 |
>>> |
| 15 |
>>> This results in no blockers, BUT, NOW it wants to update TWO versions of python-exec: |
| 16 |
>>> dev-lang/python-exec 2.0.1 AND dev-lang/python-exec-0.3.1 (to -r1). |
| 17 |
>>> |
| 18 |
>>> First question is, why does a plain emerge -pvuDN world NOT want to update both of these? |
| 19 |
>>> |
| 20 |
>>> Second questions is, do I even NEED both of these? Or can (or more importantly, SHOULD) I |
| 21 |
>>> just emerge -C dev-lang/python-exec-0.3.1? |
| 22 |
> |
| 23 |
>> dev-lang/python-exec is slotted (I have slot 0 and 2 on my system.) |
| 24 |
>> |
| 25 |
>> I assume when you do the emerge -pvuDN world it only tells you about slot 2 because there's |
| 26 |
>> only a dependency on slot 2. When you ask it to emerge dev-lang/python-exec it tries to |
| 27 |
>> emerge for all slots (I'm not sure, someone please correct me if that's not what's |
| 28 |
>> happening.) |
| 29 |
>> |
| 30 |
>> But I had a problem where something using python-exec needed to be rebuilt. Run an emerge |
| 31 |
>> -pvutDN world (add the -t option to see the tree of dependencies) and look for what wants the |
| 32 |
>> masked python-exec. Then rebuild that manually. |
| 33 |
> |
| 34 |
> Thanks... so, since it is slotted, I guess my question about needing them both is, yes, I need |
| 35 |
> them both (ie, don't emerge -C the older 0.3.1 version)... |
| 36 |
> |
| 37 |
> |
| 38 |
|
| 39 |
You really shouldn't ever `emerge -C` anything, instead using `emerge -c`, which will refuse to |
| 40 |
remove anything that might break the system in the course of its removal (due to dependencies). |
| 41 |
In fact, if you want to see what you have that is keeping a particular package on the system, you |
| 42 |
can do `emerge -pvc the/package`, which will list the reasons why the package cannot be removed. |
| 43 |
-----BEGIN PGP SIGNATURE----- |
| 44 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 45 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 46 |
|
| 47 |
iQIcBAEBCgAGBQJTG2p3AAoJELHSF2kinlg445wP/0P8ji5HLOR1WOeSfjnOzhgF |
| 48 |
1hjkjL7ciJrQkxWX6F4ZW/7b4VfiqCJM0RiKNZLlFyBjsINfnKZxGUHfm9ISE31p |
| 49 |
4DbW8idMaf5RYETd4I1PFkhdDL1PptWFIK/2lkIWu38LwtbtBkgJqv/RbkayE72q |
| 50 |
lEkCKJgYRukiwsLbdkDc0LhLjcmbW6uteWvweClPxPPekvP3arFNiJBcoOoBFeA6 |
| 51 |
KQIli6GQlEEhs/Hf9tV4NA6tiikCI8al1/FWsqmOcoslpgaQBmTlbIKjRE6WYlVb |
| 52 |
tW59wLQskIcPJ6HQ3vscqu86m0DFPSvu1RbKYNK8dK20fW8AMjIl3cV/rsXsSPKr |
| 53 |
VphKCfyw4aD5ik9blVwTV3JHu4klh8z1V0w/UVJzt6pZmh7N5sXYdXmGys3wsJxd |
| 54 |
tyiwmxRi4k5OUAWq8e8ajVBzyJS4t4N9BFlBm2U+I2JYLytm1fszAwZrtRKmUAue |
| 55 |
0Nd7dVEibuL7aVrXDQa4ztT5v/WMHP+gMeP3eKdDfkT2XBvPx+4C1A2An5eKaAHg |
| 56 |
zOJu6HjzFB56qajAoDqlcSOlkUJakW5xaluI+56MFWVEmmIx/ExX+UlNBmM+nAfm |
| 57 |
OfYCZ5DILphw69wJ0UfFwdVQHVr55WIJfr3tPEUC72u/RcGLvUQ8dFaqI37MhKn/ |
| 58 |
EUviJlPtENyeqGwX+EVZ |
| 59 |
=Scbb |
| 60 |
-----END PGP SIGNATURE----- |
Archives