1 |
On 21/01/17 16:36, Kristian Fiskerstrand wrote: |
2 |
> On 01/21/2017 10:49 AM, Michał Górny wrote: |
3 |
>> Please review the following news item. It was requested by users. |
4 |
>> Preferably I'd like to commit it today. |
5 |
> .. |
6 |
> |
7 |
>> If you are using FEATURES=collision-protect, Portage will reject |
8 |
>> the upgrade. If this is the case, please temporarily switch to |
9 |
>> FEATURES=protect-owned for the upgrade. |
10 |
>> |
11 |
>> If you are using FEATURES=protect-owned, Portage will verbosely warn |
12 |
>> about the file collisions but will proceed with the upgrade once |
13 |
>> determining no replaced files are owned. Please disregard the warning. |
14 |
> This change broke a stable system in my case without any of these features. |
15 |
> |
16 |
> world upgrade failed with * ERROR: dev-python/pycairo-1.10.0-r5::gentoo |
17 |
> failed (configure phase): due to |
18 |
> /usr/bin/env: ‘python’: No such file or directory |
19 |
> |
20 |
> system ended up with a broken symlink |
21 |
> lrwxrwxrwx 1 root root 14 Jan 21 13:55 |
22 |
> /usr/bin/python -> python-wrapper |
23 |
> |
24 |
> additionally the original upgrade, after manually setting the updated |
25 |
> symlink, ended up with a |
26 |
> python-exec: Invalid impl in /etc/python-exec/python-exec.conf: python3.3 |
27 |
> |
28 |
> How was this allowed into stable? |
29 |
> |
30 |
python3.3 has been long-gone no? |
31 |
|
32 |
But otherwise, I think this is exactly what someone was trying to forestall. |
33 |
|
34 |
How it got into the wild is another question...... |