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