Am 02.12.20 um 11:53 schrieb Julio González Gil:
On martes, 1 de diciembre de 2020 20:31:10 (CET) Michael Behrisch wrote: Your problem is different now:
[ 130s] RPM build errors: [ 130s] Installed (but unpackaged) file(s) found: [ 130s] /usr/lib/debug/usr/lib64/libCHART-1.6.so. 0.0.57-1.6.57-105.1.x86_64.debug [ 130s] /usr/lib/debug/usr/lib64/libFOX-1.6.so. 0.0.57-1.6.57-105.1.x86_64.debug
Since now you are not building the debug package anymore, you have two files that would normally go there... but they are not packaged.
My best guess is that you need to change how `%configure`, `make` or `%make_install` are called, so you don't get the debug files create, or they don't get installed.
OK, so I compared the log files and found two differences: 1. /usr/lib/rpm/find-debuginfo.sh is not called if debuginfo is disabled in the project but it is if I only use %global debug_package %{nil} 2. The opposite is true for /usr/lib/rpm/brp-strip I call neither of these scripts explicitly and I don't think they are triggered directly by the %make_install but I may be wrong. The internet says to disable find-debuginfo.sh you should set %global debug_package %{nil} https://stackoverflow.com/questions/4158692/what-does-find-debuginfo-sh-in-r... but obviously that does not do the trick. Is this a configuration bug or a change in behavior for more recent CentOS (and also Fedoras as I just noticed)? Is there more documentation what disabling debuginfo from the UI does in addition to %global debug_package %{nil} ? I would also adopt a solution which builds a proper debuginfo package instead of disabling, but I am little bit lost here as well (I found only this one: https://en.opensuse.org/openSUSE:Packaging_guidelines#Debuginfo) Thanks for your help, Michael