From: John Covici <covici@ccs.covici.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Python-3.9 and emerge problems
Date: Fri, 18 Jun 2021 09:54:09 -0400 [thread overview]
Message-ID: <m3wnqr46ta.wl-covici@ccs.covici.com> (raw)
In-Reply-To: <20210618141129.782726fd@digimed.co.uk>
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
covici@ccs.covici.com
next prev parent reply other threads:[~2021-06-18 13:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 9:46 [gentoo-user] Python-3.9 and emerge problems Jacques Montier
2021-06-18 11:20 ` John Covici
2021-06-18 11:45 ` Wols Lists
2021-06-18 12:07 ` Neil Bothwick
2021-06-18 13:11 ` Neil Bothwick
2021-06-18 13:54 ` John Covici [this message]
2021-06-18 14:00 ` Neil Bothwick
2021-06-18 14:26 ` Jacques Montier
2021-06-18 15:55 ` John Covici
2021-06-19 12:35 ` Jacques Montier
2021-06-18 13:26 ` John Covici
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3wnqr46ta.wl-covici@ccs.covici.com \
--to=covici@ccs.covici.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox