1 |
On Fri, 18 Jun 2021 09:11:29 -0400, |
2 |
Neil Bothwick wrote: |
3 |
> |
4 |
> [1 <text/plain; US-ASCII (quoted-printable)>] |
5 |
> On Fri, 18 Jun 2021 13:07:10 +0100, Neil Bothwick wrote: |
6 |
> |
7 |
> > I had the same a couple of days ago and had to downgrade portage from |
8 |
> > 3.0.20 to 3.0.18, by untarring the binary package to /. However, that |
9 |
> > needed python 3.8, so I also had to untar the binary package for that. |
10 |
> > Then I re-emerged portage-3.0.18 and python-3.8 and masked |
11 |
> > portage-3.0.20. Once I had re-emerged portage-3.0.18, it worked with |
12 |
> > python 3.9. |
13 |
> > |
14 |
> > I see that portage 3.0.20-r3 is here now, so I'll try emerging that on |
15 |
> > one system and see what happens. |
16 |
> |
17 |
> |
18 |
> Same problem with 3.0.20-r3 but then I found |
19 |
> https://bugs.gentoo.org/796584, changing sets.conf got rid of the issue. |
20 |
|
21 |
hmmm, I don't have a file like that at all, what should be in that |
22 |
file -- I don't even have a /usr/portage at all. |
23 |
|
24 |
-- |
25 |
Your life is like a penny. You're going to lose it. The question is: |
26 |
How do |
27 |
you spend it? |
28 |
|
29 |
John Covici wb2una |
30 |
covici@××××××××××.com |