binary octave packages create shared libraries with a .oct extension. rpminspect is complaining that they still contain debug symbols (see https://artifacts.dev.testing-farm.io/0b323ef4-fd4b-490a-960c-ed58066320f6/)
I've spent some time looking at the debuginfo/strip process but can't figure out why they are not getting stripped. They do have the execute bit set.
Any ideas?
On May 21, 2026 6:44:58 AM GMT+02:00, Orion Poplawski orion@nwra.com wrote:
binary octave packages create shared libraries with a .oct extension. rpminspect is complaining that they still contain debug symbols (see https://artifacts.dev.testing-farm.io/0b323ef4-fd4b-490a-960c-ed58066320f6/)
I've spent some time looking at the debuginfo/strip process but can't figure out why they are not getting stripped. They do have the execute bit set.
Any ideas?
Mkoctfile does seem to support debug symbol stripping, but I do not see it connected in the autotools [1]. Afaict these are built during the make phase right? Don't know if there is a generic flag where you can pass more flags to mkoctfile.
[1]: https://github.com/search?q=repo%3Agnu-octave%2Foctave+strip+debug&type=code
On 2026/05/21 7:03, Cristian Le via devel wrote:
On May 21, 2026 6:44:58 AM GMT+02:00, Orion Poplawskiorion@nwra.com wrote:
binary octave packages create shared libraries with a .oct extension. rpminspect is complaining that they still contain debug symbols (seehttps://artifacts.dev.testing-farm.io/0b323ef4-fd4b-490a-960c-ed58066320f6/)
I've spent some time looking at the debuginfo/strip process but can't figure out why they are not getting stripped. They do have the execute bit set.
Any ideas?
Mkoctfile does seem to support debug symbol stripping, but I do not see it connected in the autotools [1]. Afaict these are built during the make phase right? Don't know if there is a generic flag where you can pass more flags to mkoctfile.
Well, it got me thinking some more, since we do not do similar stripping at the `%cmake_install`, so I am not sure if doing the strip manually would be the best since it would not land the stuff in debug* packages IIUC.
Some pointers I've found so far: - There's a debuginfo guideline on these [1] where it hints at looking into `|find-debuginfo.sh`| - There are quite a few references that tweak this [2], but I did not find a good reference about it - Was also pointed to `/usr/lib/rpm/brp-strip` and `debugedit` that interact with these, but I am not aware of those having control knobs
[1]: https://docs.fedoraproject.org/en-US/packaging-guidelines/Debuginfo/ [2]: https://sourcegraph.com/search?q=context:global+repo:src.fedoraproject.org+f...
Hi Orion,
On Wed, 2026-05-20 at 22:44 -0600, Orion Poplawski wrote:
binary octave packages create shared libraries with a .oct extension. rpminspect is complaining that they still contain debug symbols (see https://artifacts.dev.testing-farm.io/0b323ef4-fd4b-490a-960c-ed58066320f6/)
I've spent some time looking at the debuginfo/strip process but can't figure out why they are not getting stripped. They do have the execute bit set.
Any ideas?
Not immediately. Is this for a specific octave (sub)pacakge? Does this happen for all .oct files or just for some? It seems to contain a .symtab, but no .debug sections. Are those other debug sections stripped away into separate .debug files?
Maybe I should be able to figure all that out from the testing-farm link, but I am afraid I am a little clueless. If you could point me to a specific package or koji build (log) that would be helpful.
Thanks,
Mark
On 5/26/26 06:24, Mark Wielaard wrote:
Hi Orion,
On Wed, 2026-05-20 at 22:44 -0600, Orion Poplawski wrote:
binary octave packages create shared libraries with a .oct extension. rpminspect is complaining that they still contain debug symbols (see https://artifacts.dev.testing-farm.io/0b323ef4-fd4b-490a-960c-ed58066320f6/)
I've spent some time looking at the debuginfo/strip process but can't figure out why they are not getting stripped. They do have the execute bit set.
Any ideas?
Not immediately. Is this for a specific octave (sub)pacakge? Does this happen for all .oct files or just for some? It seems to contain a .symtab, but no .debug sections. Are those other debug sections stripped away into separate .debug files?
Maybe I should be able to figure all that out from the testing-farm link, but I am afraid I am a little clueless. If you could point me to a specific package or koji build (log) that would be helpful.
It appears to be the case with all .oct files - I see the same message for all binary octave-* packages.
It does seem like debuginfo packages are generated with content, so I haven't looked closely at them.
Sample koji build for octave-statistics: https://koji.fedoraproject.org/koji/buildinfo?buildID=3000314
-
Cristian Le -
Mark Wielaard -
Orion Poplawski