On Fri, 18 Jun 2021 13:07:10 +0100, Neil Bothwick wrote:

> I had the same a couple of days ago and had to downgrade portage from
> 3.0.20 to 3.0.18, by untarring the binary package to /. However, that
> needed python 3.8, so I also had to untar the binary package for that.
> Then I re-emerged portage-3.0.18 and python-3.8 and masked
> portage-3.0.20. Once I had re-emerged portage-3.0.18, it worked with
> python 3.9.
> 
> I see that portage 3.0.20-r3 is here now, so I'll try emerging that on
> one system and see what happens.


Same problem with 3.0.20-r3 but then I found
https://bugs.gentoo.org/796584, changing sets.conf got rid of the issue.


-- 
Neil Bothwick

Of all the people I've met you're certainly one of them.

Attachment: pgpR5OBXzEKpF.pgp
Description: OpenPGP digital signature

Reply via email to