Re: [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
> this is what I wrote in my initial post (I just misspelled it > -python-upgrade -) OK. Have a nice day. Roger
Re: [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
On Thu, 20 Aug 2009 21:06:15 +0200 Roger Cahn wrote: > > > Anyway, thanks for helping. > > Did you try python-updater? > > Regards > Roger > > yes, this is what I wrote in my initial post (I just misspelled it -python-upgrade -)
Re: [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
> Anyway, thanks for helping. Did you try python-updater? Regards Roger
Re: [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
Yiannis wrote: > Does gentoo have bugs!?!?!? :). No, only features. ;-) Best regards Peter K
Re: [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
On Wed, 19 Aug 2009 23:32:53 +0300 Nikos Chantziaras wrote: > On 08/19/2009 11:17 PM, Yiannis wrote: > > On Wed, 19 Aug 2009 21:30:56 +0300 > > Nikos Chantziaras wrote: > > > >> 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. > > > > I am a little confused here about what happened. After removing > > python-2.5.4-r3, # revdep-rebuilt -pv --library libpython2.5.so.1.0 > > did not rebuild dev-libs/boost-1.35.0-r2 nor > > x11-libs/vte-0.17.4-r3. Also running: > > # for file in `equery files vte`; do if [ -f $file ]; then ldd > > $file | grep python; fi; done 2>/dev/null > > # for file in `equery files boost`; do if [ -f $file ]; then ldd > > $file | grep python; fi; done 2>/dev/null > > returns nothing about python(I suppose that revdep-rebuild does > > something like this). Everything seems ok. Am I missing something > > here? > > What about just "revdep-rebuild -a" without any other options? > > Also, what portage version do you have? If it's 2.2, it should have > the new "preserved-rebuild" feature which keeps libs even if you > depclean. If yes, I can't really help, I'm on portage 2.1. > I have portage 2.1.6.13. -a does not apply on this version of revdep-rebuild. Do not bother anymore. As long as revdep-rebuild says that everything is consistent I'll count on it. It was just plain curiosity based on the different reports between python-upgrade and revdep-rebuild(could it be a python-upgrade's bug? Does gentoo have bugs!?!?!? :). Anyway, thanks for helping.
Re: [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
On Wed, 19 Aug 2009 21:30:56 +0300 Nikos Chantziaras wrote: > 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. > I am a little confused here about what happened. After removing python-2.5.4-r3, # revdep-rebuilt -pv --library libpython2.5.so.1.0 did not rebuild dev-libs/boost-1.35.0-r2 nor x11-libs/vte-0.17.4-r3. Also running: # for file in `equery files vte`; do if [ -f $file ]; then ldd $file | grep python; fi; done 2>/dev/null # for file in `equery files boost`; do if [ -f $file ]; then ldd $file | grep python; fi; done 2>/dev/null returns nothing about python(I suppose that revdep-rebuild does something like this). Everything seems ok. Am I missing something here?
Re: [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
On Wed, 19 Aug 2009 21:30:56 +0300 Nikos Chantziaras wrote: > 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. > Ah, I thought that those ebuilds would use the latest available python. I'll try that and report the result.
