On Fri, 18 Jun 2021 09:11:29 -0400,
Neil Bothwick wrote:
>
> [1 <text/plain; US-ASCII (quoted-printable)>]
> 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.
hmmm, I don't have a file like that at all, what should be in that
file -- I don't even have a /usr/portage at all.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici wb2una
cov...@ccs.covici.com
