Bug 414819 – app-admin/python-updater-0.10: keeps rebuilding <sys-devel/gdb-7.7-r1

• Product: Gentoo Linux
• Status: RESOLVED WONTFIX

[Description Dyweni 2012-05-06 04:06:14 UTC]

sys-devel/gdb-7.3.1 requires python2 if the python flag is enabled.

on my system, I have python2.7 and python3.2 installed.  I have python3.2 as my main interpreter.

python-updater reports that gdb is 'linked against old Python shared libraries found':


 *   Adding to list: sys-devel/gdb:0
 *     check: shared_linking [ Binaries linked against old Python shared libraries found:
 *       /usr/bin/gdbtui libreadline.so.6,libncurses.so.5,libz.so.1,libm.so.6,libpthread.so.0,libdl.so.2,libpython2.7.so.1.0,libc.so.6
 *       /usr/bin/gdb libreadline.so.6,libncurses.so.5,libz.so.1,libm.so.6,libpthread.so.0,libdl.so.2,libpython2.7.so.1.0,libc.so.6
 *     ]



However, as python 2.7 is valid and GDB has no options for using python3, I think python-updater should not be rebuilding GDB.




Reproducible: Always

Steps to Reproduce:
1. python-updater -v -- -p
Actual Results:  
python-updater is requesting to rebuild GDB

Expected Results:  
python-updater should not be requesting to rebuild GDB

[Comment 1 Arfrever Frehtes Taifersar Arahesis 2012-05-06 23:26:38 UTC]

sys-devel/gdb should use 'python_set_active_version 2'.

[Comment 2 Mike Gilbert 2012-05-09 02:51:11 UTC]

Is there a solution that does not involve inheriting python.eclass?

[Comment 3 MCassaniti 2012-10-29 02:21:34 UTC]

I can also confirm this as an issue. When I check the ChangeLog for python-updater there is no mention of this patch or thread. I also find it concerning that this issue is marked unconfirmed even though it is assigned to the Python Gentoo team.

Can someone upstream please take a look over this and see what can be done. This issue has been outstanding for over 5 months.

[Comment 4 Rick Farina (Zero_Chaos) 2014-05-19 17:33:08 UTC]

gdb 7.7-r1 and 7.7.1 are using python-single-r1 which will fix this issue.  Is there any chance of getting them stabilized? or backporting the class usage to a version toolchain is willing to stabilize?

[Comment 5 SpanKY 2014-05-25 00:02:01 UTC]

we're not backporting things, and newer versions will get stabilized like normal.  i don't see a reason to rush this.

[Comment 6 Rick Farina (Zero_Chaos) 2014-05-25 14:03:54 UTC]

Please don't resolve fixed things that aren't fixed in stable. If you don't want to rush stabilization and you refuse to backport simple ebuild changes without giving a reason, may I backport the ebuild fixes for you? It seems easy enough.

[Comment 7 Mike Gilbert 2014-05-25 22:10:03 UTC]

There is no rule that says bugs must remain open until the rebuild is stabilized.

Please file a stable request bug, or reassign this appropriately.