public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
Date: Sat, 19 Dec 2020 15:49:34 +0000	[thread overview]
Message-ID: <20201219154934.3c2ecd0d@digimed.co.uk> (raw)
In-Reply-To: <479117a7-1101-5463-da94-13a5d7c232f0@web.de>

[-- Attachment #1: Type: text/plain, Size: 1711 bytes --]

On Sat, 19 Dec 2020 15:19:22 +0100, n952162 wrote:

> On 12/19/20 12:35 PM, Neil Bothwick wrote:
> > On Sat, 19 Dec 2020 12:12:21 +0100, n952162 wrote:
> >  
> >>> 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.  
> >>
> >> depclean output attached.
> >>  
> >>   >>> No packages selected for removal by depclean  
> >> Packages installed:   899
> >> Packages in world:    291
> >> Packages in system:   43
> >> Required packages:    899
> >> Number removed:       0  
> > Which means the package is in @world, so just remove it with "emerge
> > -cav ipaddress".
> 
> $ sudo emerge -cav ipaddress  2>&1 | tee ipaddress-clean.$ymd
> Password:
> 
> Calculating dependencies  .... done!
>    dev-python/ipaddress-1.0.23 pulled in by:
>      dev-python/cryptography-2.9 requires
> dev-python/ipaddress[python_targets_python2_7(-),-python_single_target_python2_7(-)]
>      dev-python/urllib3-1.25.10 requires
> dev-python/ipaddress[python_targets_python2_7(-),-python_single_target_python2_7(-)]
> 
>  >>> No packages selected for removal by depclean  
> Packages installed:   899
> Packages in world:    287
> Packages in system:   43
> Required packages:    899
> Number removed:       0

dev-python/cryptography-2.9 is no longer in the tree, it's an old python
2.7 package. Update it then you can remove ipaddress.


-- 
Neil Bothwick

Eye of newt, toe of frog, regular Coke and fries to go, please.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-12-19 15:49 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 [this message]
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=20201219154934.3c2ecd0d@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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