public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Gerrit Kuehn <gerrit.kuehn@aei.mpg.de>
To: Michael Orlitzky <mjo@gentoo.org>
Cc: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] python, my nemesis
Date: Mon, 20 Sep 2021 16:31:59 +0200	[thread overview]
Message-ID: <20210920163159.54851d8a@comet2.terra.ger> (raw)
In-Reply-To: <433d956b8fd9e0bbaba4596848094149110adf48.camel@gentoo.org>


On Mon, 20 Sep 2021 09:18:23 -0400
Michael Orlitzky <mjo@gentoo.org> wrote:

> With our package manager written in python, you often need old python
> stuff to build the new python stuff, and disabling the old python
> stuff will throw a wrench into that. Even in situations where
> technically some upgrade path exists, the complexity of the python
> dependencies often means that the package manager will give up before
> it finds the solution unless the solution is obvious. By tweaking
> those variables, you make the solution less obvious to it.

I took out the extra settings and solved a few conflicts manually. I'm
down to this now:

---
 ~ # emerge -p --oneshot sys-apps/portage --verbose-conflicts

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N     ] acct-group/portage-0 
[ebuild  N     ] acct-user/portage-0 
[ebuild     U  ] sys-apps/portage-3.0.20-r6 [3.0.4-r1]
PYTHON_TARGETS="python3_9* (-python3_10)" 

!!! Multiple package instances within a single package slot have been
pulled !!! into the dependency graph, resulting in a slot conflict:

sys-apps/portage:0

  (sys-apps/portage-3.0.20-r6:0/0::gentoo, ebuild scheduled for merge)
  USE="(ipc) native-extensions rsync-verify xattr -apidoc -build -doc
  -gentoo-dev (-selinux) -test" ABI_X86="(64)"
  PYTHON_TARGETS="python3_9 (-pypy3) (-python3_10) -python3_8" pulled
  in by sys-apps/portage (Argument)

  (sys-apps/portage-3.0.4-r1-3:0/0::gentoo, installed) USE="(ipc)
  native-extensions rsync-verify xattr -apidoc -build -doc -gentoo-dev
  (-selinux) -test" ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3)
  -python3_6 -python3_8 -python3_9" pulled in by
  sys-apps/portage[python_targets_python3_7(-),-python_single_target_pypy3(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-)]
  required by (app-portage/gentoolkit-0.5.0:0/0::gentoo, installed)
  USE="-test" ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3)
  -python3_6 -python3_8" 
---


This looks like portage is blocked by itself... so how to solve this
one?


cu
  Gerrit


  parent reply	other threads:[~2021-09-20 14:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-20 12:50 [gentoo-user] python, my nemesis Gerrit Kuehn
2021-09-20 13:18 ` Michael Orlitzky
2021-09-20 13:56   ` Gerrit Kuehn
2021-09-20 14:29     ` Michael
2021-09-20 14:52       ` Gerrit Kuehn
2021-09-20 15:20         ` Michael
2021-09-20 15:40           ` Gerrit Kuehn
2021-09-20 16:02           ` Laurence Perkins
2021-09-20 17:19       ` [gentoo-user] " Grant Edwards
2021-09-21 16:29         ` Gerrit Kuehn
2021-09-20 14:34     ` [gentoo-user] " Michael Orlitzky
2021-09-20 15:00       ` Gerrit Kuehn
2021-09-20 15:17     ` Neil Bothwick
2021-09-20 15:30       ` Gerrit Kuehn
2021-09-20 15:47       ` Laurence Perkins
2021-09-20 14:31   ` Gerrit Kuehn [this message]
2021-09-20 14:40     ` Gerrit Kuehn
2021-09-20 14:41     ` Arve Barsnes
2021-09-20 14:58       ` Gerrit Kuehn

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=20210920163159.54851d8a@comet2.terra.ger \
    --to=gerrit.kuehn@aei.mpg.de \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=mjo@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