public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Arve Barsnes <arve.barsnes@gmail.com>
To: Gentoo <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
Date: Sat, 19 Dec 2020 11:56:15 +0100	[thread overview]
Message-ID: <CAJjrzcXcW9_jSMpLHHeb8PXr44L7V6+3s-WaZOAxPmHPg7mReQ@mail.gmail.com> (raw)
In-Reply-To: <f9a508dc-ee6c-369a-b8fe-101d60ab0700@web.de>

On Sat, 19 Dec 2020 at 11:19, n952162 <n952162@web.de> wrote:
> I don't think this output or any list participant has actually identified where the problem here is.  In my original posting, the only difference causing the slot collision for jinja was that one had a PYTHON_TARGETS of 3-7 and the other of 3-8.  I asked how to force it to the correct value, but if someone explained that to me, I didn't understand it.


Your output gives away that you STILL have not run depclean, so you
STILL have dev-python/ipaddress installed, which has been removed from
the tree, and requires python 2.7. Unless you remove old broken
software you will NEVER get through a world update.

Also: don't set PYTHON_TARGETS unless you have a REALLY good reason.
You can set it on a specific package (and preferrable to set it only
on a specific version of that package) to go around problems, but
DON'T do this until you have made your system sane (meaning you can
run world updates without troubles).

Regards,
Arve


  parent reply	other threads:[~2020-12-19 10:56 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
2020-12-19 11:15         ` n952162
2020-12-19 10:56       ` Arve Barsnes [this message]
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=CAJjrzcXcW9_jSMpLHHeb8PXr44L7V6+3s-WaZOAxPmHPg7mReQ@mail.gmail.com \
    --to=arve.barsnes@gmail.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