After update and deinstallation of python-2.4 i found that there is a library in media-libs/alsa-lib that links to python: # ldd /usr/lib/alsa-lib/smixer/smixer-python.so linux-gate.so.1 => (0xb8020000) libpthread.so.0 => /lib/libpthread.so.0 (0xb7fec000) libdl.so.2 => /lib/libdl.so.2 (0xb7fe8000) libutil.so.1 => /lib/libutil.so.1 (0xb7fe4000) libm.so.6 => /lib/libm.so.6 (0xb7fbe000) libpython2.4.so.1.0 => not found libasound.so.2 => /usr/lib/libasound.so.2 (0xb7f0b000) libc.so.6 => /lib/libc.so.6 (0xb7dd3000) /lib/ld-linux.so.2 (0xb8021000) librt.so.1 => /lib/librt.so.1 (0xb7dca000) As far as i can see it is not specified in dependencies. Maybe there is configure option to disable it. Reproducible: Always
alsa-lib has an optional python dependency, which is reflected via an use flag. You probably didn't run "python-updater" after updating Python. Now you've unmerged python 2.4 prematurely you've to run it with "-o 2.4" Assuming invalid. Feel free to reopen, in case you think I'm wrong.
Ahh, i see. There is USE="python" but only in media-libs/alsa-lib-1.0.16-r1, which currently is unstable. Current stable version has this issue... i don't know how to handle this (maybe stabilization?) so i reopen. I didn't run python-updater, only reconcillo to check packages linked to old python version and this is how i did found this.
(In reply to comment #2) > Ahh, i see. There is USE="python" but only in media-libs/alsa-lib-1.0.16-r1, > which currently is unstable. Current stable version has this issue... i don't > know how to handle this (maybe stabilization?) so i reopen. Indeed, yes. Missed that. > I didn't run python-updater, only reconcillo to check packages linked to old > python version and this is how i did found this. You'll face issues not only bould to linking. Running python-updater after a major Python update is not optional.
(In reply to comment #3) > > I didn't run python-updater, only reconcillo to check packages linked to old > > python version and this is how i did found this. > > You'll face issues not only bould to linking. Running python-updater after a > major Python update is not optional. > Thanks for this clarification.
The bug title and bug contents don't coincide, so I'm going to file a new bug instead of retitling this one. Not quite sure what happened, but the bug looks invalid to me.
