ruby-debuginfo.x86_64: W: unstripped-binary-or-object /usr/lib/debug/.dwz/ruby-3.1.0-1.fc36.x86_64

[voxik]

I typically use rpmlint this way:

$ rpmlint -r ./ruby.rpmlintrc ./ruby.spec /var/lib/mock/ruby/result/ruby*.rpm

I.e. I check the .spec file I develop as well as the mock build results. Unfortunately, the output contains a lot of warnigns:

... snip ...

ruby-bundled-gems-debuginfo.x86_64: W: unstripped-binary-or-object /usr/lib/debug/usr/lib64/gems/ruby/debug-1.4.0/debug/debug.so-3.1.0-1.fc36.x86_64.debug
ruby-debuginfo.x86_64: W: unstripped-binary-or-object /usr/lib/debug/.dwz/ruby-3.1.0-1.fc36.x86_64
ruby-debuginfo.x86_64: W: unstripped-binary-or-object /usr/lib/debug/usr/bin/ruby-mri-3.1.0-1.fc36.x86_64.debug
ruby-libs-debuginfo.x86_64: W: unstripped-binary-or-object /usr/lib/debug/usr/lib64/libruby.so.3.1.0-3.1.0-1.fc36.x86_64.debug
ruby-libs-debuginfo.x86_64: W: unstripped-binary-or-object /usr/lib/debug/usr/lib64/ruby/cgi/escape.so-3.1.0-1.fc36.x86_64.debug

... snip ...

Obviously, these are *-debuginfo packages and they are expected to contain debug information, therefore rpmlint should handle them better

[voxik]

BTW there are also other warnings reported for -debuginfo:

... snip ...

ruby-bundled-gems-debuginfo.x86_64: W: dangling-relative-symlink /usr/lib/debug/.build-id/a2/bb968b5abd3d3c97308bc41a6f4cfc7204c09a ../../../.build-id/a2/bb968b5abd3d3c97308bc41a6f4cfc7204c09a
ruby-debuginfo.x86_64: W: dangling-relative-symlink /usr/lib/debug/.build-id/31/59ebbe346871776164d429fb3b5c64c9251ed1 ../../../.build-id/31/59ebbe346871776164d429fb3b5c64c9251ed1
ruby-libs-debuginfo.x86_64: W: dangling-relative-symlink /usr/lib/debug/.build-id/00/7358ffff6631bcddd9246f9f36b810dd6c4238 ../../../.build-id/00/7358ffff6631bcddd9246f9f36b810dd6c4238

... snip ...

[marxin]

Note one should not call rpmlint for debug info packages.