Bug 1212909

Summary: unstripped-binary-or-object for binary libraries in Python directories
Product: [openSUSE] openSUSE Tumbleweed Reporter: Matej Cepl <mcepl>
Component: PythonAssignee: Daniel Garcia <daniel.garcia>
Status: RESOLVED WONTFIX QA Contact: E-mail List <qa-bugs>
Severity: Enhancement    
Priority: P4 - Low CC: daniel.garcia
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Matej Cepl 2023-07-01 09:10:04 UTC
There is a zillion packages which end up with the warning like

python311-scipy.x86_64: W: unstripped-binary-or-object /usr/lib64/python3.11/site-packages/scipy/spatial/_qhull.cpython-311-x86_64-linux-gnu.so

(this is from https://build.opensuse.org/package/live_build_log/home:gladiac:mailman/python-scipy/openSUSE_Tumbleweed/x86_64)

Interestingly the same package in the devel project doesn’t seem to present the same problem (https://build.opensuse.org/build/devel:languages:python:numeric/openSUSE_Tumbleweed/x86_64/python-scipy/_log).

Could we find out why these happen and do something about it?
Comment 1 Daniel Garcia 2023-07-14 06:17:04 UTC
I've detected that this happens when the project configuration in obs has

<debuginfo><disabled/></debuginfo>

In that case the rpmbuild command is run with "--undefine _enable_debug_packages" and looks like this is the cause of non fully stripped binaries.

When the debuginfo is enabled the script /usr/lib/rpm/find-debuginfo is run and for each .so file it runs objcopy with the --strip-all flag.

The brp-15-strip-debug [1] script is run even if the debuginfo is disabled, but looks like this script doesn't strip all the symbols so just with this, rpmlint find the 'no stripped' string in the file magic.

[1] https://github.com/openSUSE/brp-check-suse/blob/master/brp-15-strip-debug#L29
Comment 2 Daniel Garcia 2024-06-07 06:03:30 UTC
I think we can close this bug. This warning is related to the project configuration and building with debuginfo enabled. In that case this warning can be ignored.

Detailed info in comment #1