public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: james <garftd@verizon.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] python targets problem
Date: Sat, 25 Aug 2018 13:57:48 -0400	[thread overview]
Message-ID: <85c16c8f-c410-fe04-c3bc-b324743e9165@verizon.net> (raw)
In-Reply-To: <20180825083328.GC2345@ca.inter.net>

Here is some information that may help::

https://wiki.gentoo.org/wiki/Project:Python/Dependencies

It also often helps to just read the ebuilds relevant to the issues
you encounter. For example:

less /usr/portage/dev-python/setuptools/setuptools-36.7.2.ebuild

It's a pita, but as packages are listed in ebuild, check them out
(manually) on your system.


I had some issue with Python of late, and just settled  on the defaults
2.7 && 3.5 and they all cleaned up nicely.


https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS
https://wiki.gentoo.org/wiki/Project:Python/Implementations


hth,
James

On 8/25/18 4:33 AM, Philip Webb wrote:
> For a long time, several pkgs have been refusing to install,
> apparently due to a conflict re python targets :
> 
> root:595 ~> emerge -pv certifi file pyblake2 meson setuptools   
> Calculating dependencies... done!
> [ebuild   R    ] dev-python/setuptools-36.7.2  PYTHON_TARGETS="-python3_4* -python3_5* python3_6*" 
> [ebuild     U  ] dev-python/certifi-2018.4.16 [2017.4.17] PYTHON_TARGETS="-python3_4* -python3_5* python3_6* (-python3_7)" 
> [ebuild     U  ] sys-apps/file-5.33-r4 [5.32] PYTHON_TARGETS="-python3_4* python3_6* (-python3_7)" 
> [ebuild     U  ] dev-python/pyblake2-1.1.2 [1.1.0] PYTHON_TARGETS="(-pypy3) -python3_4* -python3_5* python3_6* (-python3_7)" 
> [ebuild     U  ] dev-util/meson-0.46.1 [0.45.1] PYTHON_TARGETS="-python3_5* python3_6*" 
> 
> !!! Multiple package instances within a single package slot have been pulled
> !!! into the dependency graph, resulting in a slot conflict:
> 
> dev-python/setuptools:0
>   (dev-python/setuptools-36.7.2:0/0::gentoo, ebuild scheduled for merge) pulled in by
>     dev-python/setuptools[python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (dev-util/meson-0.46.1:0/0::gentoo, ebuild scheduled for merge)
> 
>     dev-python/setuptools[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (sys-apps/file-5.33-r4:0/0::gentoo, ebuild scheduled for merge)
> 
>     dev-python/setuptools (Argument)
>     dev-python/setuptools[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (dev-python/pyblake2-1.1.2:0/0::gentoo, ebuild scheduled for merge)
> 
>     dev-python/setuptools[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (dev-python/certifi-2018.4.16:0/0::gentoo, ebuild scheduled for merge)
> 
>   (dev-python/setuptools-36.7.2:0/0::gentoo, installed) pulled in by
>     dev-python/setuptools[python_targets_python2_7(-),python_targets_python3_4(-),python_targets_python3_5(-),-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (dev-python/certifi-2017.4.17:0/0::gentoo, installed)
> 
>     dev-python/setuptools[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (dev-python/pygments-2.2.0:0/0::gentoo, installed)
> 
> dev-python/certifi:0
> 
>   (dev-python/certifi-2018.4.16:0/0::gentoo, ebuild scheduled for merge) pulled in by
>     dev-python/certifi (Argument)
>     >=dev-python/certifi-2016.9.26[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (dev-python/setuptools-36.7.2:0/0::gentoo, ebuild scheduled for merge)
> 
>   (dev-python/certifi-2017.4.17:0/0::gentoo, installed) pulled in by
>     >=dev-python/certifi-2016.9.26[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (dev-python/setuptools-36.7.2:0/0::gentoo, installed)
> 
> Can anyone else read this mess & advise what to do ?
> Perhaps just leave well along ... (smile)
> 



      parent reply	other threads:[~2018-08-25 17:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-25  8:33 [gentoo-user] python targets problem Philip Webb
2018-08-25  9:00 ` Corentin “Nado” Pazdera
2018-08-25 16:53 ` [gentoo-user] " Nuno Silva
2018-08-25 17:57 ` james [this message]

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=85c16c8f-c410-fe04-c3bc-b324743e9165@verizon.net \
    --to=garftd@verizon.net \
    --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