From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-194160-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by finch.gentoo.org (Postfix) with ESMTPS id D72381382C5
	for <garchives@archives.gentoo.org>; Tue,  8 Dec 2020 10:00:24 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id E6BA0E0877;
	Tue,  8 Dec 2020 10:00:20 +0000 (UTC)
Received: from smarthost01d.mail.zen.net.uk (smarthost01d.mail.zen.net.uk [212.23.1.7])
	(using TLSv1.2 with cipher DHE-RSA-AES128-SHA256 (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 8AE25E084A
	for <gentoo-user@lists.gentoo.org>; Tue,  8 Dec 2020 10:00:20 +0000 (UTC)
Received: from [82.69.80.10] (helo=peak.localnet)
	by smarthost01d.mail.zen.net.uk with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
	(Exim 4.80)
	(envelope-from <peter@prh.myzen.co.uk>)
	id 1kmZn9-0008I6-1B
	for gentoo-user@lists.gentoo.org; Tue, 08 Dec 2020 10:00:19 +0000
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] portage blocking portage update
Date: Tue, 08 Dec 2020 10:00:18 +0000
Message-ID: <4302568.LvFx2qVVIh@peak>
In-Reply-To: <CAJjrzcV4TxXKbVFyi6ou1ux_RiHKaZ8doTkm+oVMzp0TnaOP9g@mail.gmail.com>
References: <20201208090718.GA16745@waltdnes.org> <CAJjrzcV4TxXKbVFyi6ou1ux_RiHKaZ8doTkm+oVMzp0TnaOP9g@mail.gmail.com>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Originating-smarthost01d-IP: [82.69.80.10]
Feedback-ID: 82.69.80.10
X-Archives-Salt: e0dbe539-a468-44af-9637-c42bc4ec6a39
X-Archives-Hash: 2520253f9f0cf3741be33c09c448ec90

On Tuesday, 8 December 2020 09:38:43 GMT 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.

Agreed. That's what I did: just updated as usual and all went tickety-boo.

-- 
Regards,
Peter.