Red Hat Bugzilla – Bug 713598
python-async-debuginfo is empty
Last modified: 2013-01-10 01:37:41 EST
python-async-debuginfo is empty. Should the package be actually noarch (yep, it installs to /usr/lib64 on x86_64, but should it)?
If not, the debuginfo package should be explicitly disabled if there's nothing to extract debuginfo from.
It builds a binary python module that is arch dependent. What's the right way to prevent a debuginfo package from being automatically generated?
(In reply to comment #1)
> It builds a binary python module that is arch dependent.
Ah, I see that's the intention from the build logs, but it actually fails to do that:
gcc -pthread -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -fPIC -I/usr/include/python2.7 -c mod/zlibmodule.c -o build/temp.linux-x86_64-2.7/mod/zlibmodule.o
mod/zlibmodule.c:8:18: fatal error: zlib.h: No such file or directory
Ignored failure when building extensions, pure python modules will be used instead
Adding "BuildRequires: zlib-devel" fixes that, and results in proper debuginfo as well.
> What's the right way to prevent a debuginfo package from being automatically
Following the links in the DebugInfo bug this one blocks:
...but there's no need to do anything about the debuginfo package after the zlib-devel BR fix.
Ooooh! Good catch! I didn't see this in my local builds due to having zlib-devel installed. I'll fix this right away.