public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: dev-libs/boost-1.35.0-r2 and x11-libs/vte-0.17.4-r3 still linked to   libpython2.5.so.1.0 after upgrading to python-2.6.2-r1
Date: Wed, 19 Aug 2009 21:30:56 +0300	[thread overview]
Message-ID: <h6hgcs$tgj$1@ger.gmane.org> (raw)
In-Reply-To: <20090819211356.0bf8fb1e@mpismpirikos.tolises.homeunix.org>

On 08/19/2009 09:13 PM, Yiannis wrote:
> Hello,
>
> Recently I upgraded to python-2.6.2-r1 which currently is slotted on
> my system as long as python-2.5.4-r3 is. After running python-upgrade
> twice I see that dev-libs/boost-1.35.0-r2 and x11-libs/vte-0.17.4-r3
> are still linked to libpython2.5.so.1.0. On the other hand emege
> --depclean -p suggests that python-2.5.4-r3 can be removed and this is
> what I would like to do if possible. Shouldn't python-upgrade have
> resolved this linking issue? From the afore mentioned ebuilds I can
> tell that there is no specific dependency on python 2.5. Any help would
> be appreciated.

That's what revdep-rebuild is for.  After depclean removes python-2.5, 
you need to do a revdep-rebuild which will take care of boost and any 
other packages still using the old libpython.




  reply	other threads:[~2009-08-19 18:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-19 18:13 [gentoo-user] dev-libs/boost-1.35.0-r2 and x11-libs/vte-0.17.4-r3 still linked to libpython2.5.so.1.0 after upgrading to python-2.6.2-r1 Yiannis
2009-08-19 18:30 ` Nikos Chantziaras [this message]
2009-08-19 18:41   ` [gentoo-user] " Yiannis
2009-08-19 20:17   ` Yiannis
2009-08-19 20:32     ` Nikos Chantziaras
2009-08-19 21:12       ` Yiannis
2009-08-19 22:50         ` pk
2009-08-20 19:06         ` Roger Cahn
2009-08-20 23:07           ` Yiannis
2009-08-21 10:21             ` Roger Cahn

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='h6hgcs$tgj$1@ger.gmane.org' \
    --to=realnc@arcor.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