public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: n952162 <n952162@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
Date: Sat, 19 Dec 2020 10:39:14 +0100	[thread overview]
Message-ID: <87632e25-0aa7-f6f7-e25a-1874cfa9fd77@web.de> (raw)
In-Reply-To: <CAM8Dd_2J1xVvM++oDA0+Ts6cjw_QrBX_K8-6ZyQj1ocWo-qDPw@mail.gmail.com>

On 12/16/20 11:34 AM, Miles Malone 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?
>
That's how I started this process.  That failed, and I tried cutting
back the scope of the emerge, but it hasn't helped.



  parent reply	other threads:[~2020-12-19  9:38 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
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 [this message]
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=87632e25-0aa7-f6f7-e25a-1874cfa9fd77@web.de \
    --to=n952162@web.de \
    --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