From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
Date: Sat, 19 Dec 2020 18:45:00 +0800 [thread overview]
Message-ID: <d8e62bda-095a-06bf-021c-153a8e81ac5d@iinet.net.au> (raw)
In-Reply-To: <f9a508dc-ee6c-369a-b8fe-101d60ab0700@web.de>
On 19/12/20 6:20 pm, n952162 wrote:
> On 12/16/20 11:59 AM, Arve Barsnes wrote:
>> On Wed, 16 Dec 2020 at 11:34, Miles Malone
>> <m.malone@homicidalteddybear.net> wrote:
>>> What's happening when you do emerge -avuDN --with-bdeps=y
>>> --backtrack=100 @world ? Giving portage the flexibility to solve it
>>> with some extra backtracking and increasing the scope to world might
>>> fix it, if not then we can revisit it?
>> You should definitely try this first if you haven't.
>
>
> I have.
>
> ...
Backtracking rarely helps in my experience.
check the blocks: using --nodeps forces the install, then it may work
(you may have to add to package.accept_keywords etc. to cover that angle
- but I am on arm and arm64 where the most difficult of the python
problems happened for me)
I also have:
USE_PYTHON="3.8"
PYTHON_TARGETS="python3_8"
PYTHON_SINGLE_TARGET="python3_8"
*** a number of packages from overlays I am using don't like 3.9 so I
removed it)
I have a number of intel, arm and arm64 and virtualised systems and all
have problems with python in some way or other - I could only remove the
python targets on a couple of them. After a mass update, I have been
trying to remove the targets but its only working for a few so far, and
they are not stable.
I wish python would just go away and perl gets brought back - a lot less
drama ...
BillK
next prev parent reply other threads:[~2020-12-19 10:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 10:24 [gentoo-user] override PYTHON_TARGETS to avoid a slot collision n952162
2020-12-16 10:34 ` Miles Malone
2020-12-16 10:59 ` Arve Barsnes
2020-12-19 10:20 ` n952162
2020-12-19 10:45 ` William Kenworthy [this message]
2020-12-19 11:15 ` n952162
2020-12-19 10:56 ` Arve Barsnes
2020-12-19 11:12 ` n952162
2020-12-19 11:35 ` Neil Bothwick
2020-12-19 14:19 ` n952162
2020-12-19 15:49 ` Neil Bothwick
2020-12-19 12:34 ` Arve Barsnes
2020-12-19 11:12 ` bobwxc
2020-12-19 11:33 ` n952162
2020-12-19 11:37 ` Neil Bothwick
2020-12-19 11:51 ` Michael
2020-12-19 12:02 ` Jude DaShiell
2020-12-19 11:35 ` Michael
2020-12-19 14:11 ` n952162
2020-12-19 15:54 ` Neil Bothwick
2020-12-19 16:13 ` Dale
2020-12-20 13:58 ` Róbert Čerňanský
2020-12-16 11:07 ` n952162
2020-12-16 11:20 ` Miles Malone
2020-12-16 11:22 ` Miles Malone
2020-12-16 12:25 ` Dale
2020-12-19 9:39 ` n952162
2020-12-16 10:56 ` bobwxc
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=d8e62bda-095a-06bf-021c-153a8e81ac5d@iinet.net.au \
--to=billk@iinet.net.au \
--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