1 |
On Wed, 19 Aug 2009 21:30:56 +0300 |
2 |
Nikos Chantziaras <realnc@×××××.de> wrote: |
3 |
|
4 |
> On 08/19/2009 09:13 PM, Yiannis wrote: |
5 |
> > Hello, |
6 |
> > |
7 |
> > Recently I upgraded to python-2.6.2-r1 which currently is slotted on |
8 |
> > my system as long as python-2.5.4-r3 is. After running |
9 |
> > python-upgrade twice I see that dev-libs/boost-1.35.0-r2 and |
10 |
> > x11-libs/vte-0.17.4-r3 are still linked to libpython2.5.so.1.0. On |
11 |
> > the other hand emege --depclean -p suggests that python-2.5.4-r3 |
12 |
> > can be removed and this is what I would like to do if possible. |
13 |
> > Shouldn't python-upgrade have resolved this linking issue? From the |
14 |
> > afore mentioned ebuilds I can tell that there is no specific |
15 |
> > dependency on python 2.5. Any help would be appreciated. |
16 |
> |
17 |
> That's what revdep-rebuild is for. After depclean removes |
18 |
> python-2.5, you need to do a revdep-rebuild which will take care of |
19 |
> boost and any other packages still using the old libpython. |
20 |
> |
21 |
|
22 |
Ah, I thought that those ebuilds would use the latest available python. |
23 |
I'll try that and report the result. |