From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] portage blocking portage update
Date: Tue, 8 Dec 2020 11:39:56 -0500 [thread overview]
Message-ID: <20201208163956.GA18589@waltdnes.org> (raw)
In-Reply-To: <CAJjrzcV4TxXKbVFyi6ou1ux_RiHKaZ8doTkm+oVMzp0TnaOP9g@mail.gmail.com>
On Tue, Dec 08, 2020 at 10:38:43AM +0100, Arve Barsnes wrote
> On Tue, 8 Dec 2020 at 10:07, Walter Dnes <waltdnes@waltdnes.org> wrote:
> > I just did an "emerge --sync", and was told to update portage. But it
> > seems that portage 3.0.8 built with python 3.7 is blocking portage 3.0.9
> > with python 3.8. I obviously can't remove portage to fix the block <G>.
> > Note "grep -i python /etc/portage/make.conf" shows no output at all. In
> > package.use, PYTHON_TARGETS: and PYTHON_SINGLE_TARGET: are commented out.
>
> It's a dependency problem that I find that it is not worth to
> untangle. I had the exact same problem yesterday on a different
> machine.
>
> My advice: skip this and go straight to world update. portage will
> most likely figure out the tangle for you, and update itself during
> the world update.
Thank you. That fixed the problem. After updating world portage-3.0.9
is now installed, built against PYTHON_TARGETS="python3_8"
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
prev parent reply other threads:[~2020-12-08 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 9:07 [gentoo-user] portage blocking portage update Walter Dnes
2020-12-08 9:38 ` Arve Barsnes
2020-12-08 10:00 ` Peter Humphrey
2020-12-08 16:39 ` Walter Dnes [this message]
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=20201208163956.GA18589@waltdnes.org \
--to=waltdnes@waltdnes.org \
--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