1 |
Sorry sorry sorry… |
2 |
|
3 |
Franz is right... |
4 |
|
5 |
Do not uninstall all python versions ! |
6 |
|
7 |
|
8 |
Hogren |
9 |
|
10 |
On 24/08/2020 11:39, Franz Fellner wrote: |
11 |
> On Mo 24 Aug 2020 11:21:10 +0200, Hogren <hogren@×××××.com> wrote: |
12 |
>> Maybe try to : |
13 |
>> |
14 |
>> - Unmerge all python and python-setuptools versions |
15 |
> No, don't do that!!! |
16 |
> Unmerging all python version will leave you with a non-working portage. |
17 |
> portage is written in python. |
18 |
> You can fix that but it requires some manual intervention... |
19 |
> |
20 |
>> - Verify your package.use files. Run "grep -Ri 'python' |
21 |
>> /etc/portage/package.use/" and delete old files. |
22 |
>> |
23 |
>> - Run a "emerge --newuse --update --autounmask-write --deep |
24 |
>> --with-bdeps=y @world". |
25 |
> This should be the first thing to check. |
26 |
> package.use and probably also make.conf should be looked for PYTHON settings. |
27 |
> Uncomment affected lines first (put the character # at the beginning) before deleting. |
28 |
> The "--deep --newuse" emerge options should take care for the rest. |
29 |
> |