| 1 |
On Fri, 18 Jun 2021 13:07:10 +0100, Neil Bothwick wrote: |
| 2 |
|
| 3 |
> I had the same a couple of days ago and had to downgrade portage from |
| 4 |
> 3.0.20 to 3.0.18, by untarring the binary package to /. However, that |
| 5 |
> needed python 3.8, so I also had to untar the binary package for that. |
| 6 |
> Then I re-emerged portage-3.0.18 and python-3.8 and masked |
| 7 |
> portage-3.0.20. Once I had re-emerged portage-3.0.18, it worked with |
| 8 |
> python 3.9. |
| 9 |
> |
| 10 |
> I see that portage 3.0.20-r3 is here now, so I'll try emerging that on |
| 11 |
> one system and see what happens. |
| 12 |
|
| 13 |
|
| 14 |
Same problem with 3.0.20-r3 but then I found |
| 15 |
https://bugs.gentoo.org/796584, changing sets.conf got rid of the issue. |
| 16 |
|
| 17 |
|
| 18 |
-- |
| 19 |
Neil Bothwick |
| 20 |
|
| 21 |
Of all the people I've met you're certainly one of them. |
Archives