When viewing the contents of the jss RPM:
# rpm -ql jss /usr/lib/.build-id /usr/lib/.build-id/ca /usr/lib/.build-id/ca/2b8af38bba6252100c2d6c2f55f1a6681d3ed2 /usr/lib/java/jss4.jar /usr/lib64/jss/jss4.jar /usr/lib64/jss/libjss4.so /usr/share/doc/jss /usr/share/doc/jss/MPL-1.1.txt /usr/share/doc/jss/gpl.txt /usr/share/doc/jss/jss.html /usr/share/doc/jss/lgpl.txt
the following files should NOT be a part of the RPM:
/usr/lib/.build-id /usr/lib/.build-id/ca /usr/lib/.build-id/ca/2b8af38bba6252100c2d6c2f55f1a6681d3ed2
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 4.4.4
Metadata Update from @mharmsen: - Issue assigned to edewata
@mharmsen So I think they're supposed to be part of the RPM. This is described (in Fedora) in the RFC.
Even a "traditional" Java project such as eclipse has these files:
eclipse
$ rpm -ql eclipse-platform | grep build-id /usr/lib/.build-id /usr/lib/.build-id/09 /usr/lib/.build-id/09/e1ec44fd1cb283d30c9889a48c4e5820e21ce3 /usr/lib/.build-id/3f /usr/lib/.build-id/3f/50d0672ed206bbdb1c22727084aa9bdf34b830 /usr/lib/.build-id/4f /usr/lib/.build-id/4f/52d4510a37c7b5a71579fd9407402f6b0811fc /usr/lib/.build-id/76 /usr/lib/.build-id/76/ac6aa1d26e7484306b9535e3449e4e91872f45 /usr/lib/.build-id/a0 /usr/lib/.build-id/a0/be4c21b690bc4a8eef99efb658549d32623724
These come about as a result of the compiled library, libjss4.so, and allow us to link the debuginfo package to the library, and make magic happen with gdb if we ever need to step through the program with gdb.
libjss4.so
gdb
$ rpm -ql ~/build/jss/RPMS/jss-4.* /usr/lib/.build-id /usr/lib/.build-id/3f /usr/lib/.build-id/3f/4af84b1095db43b47021b43ce3753c8a599041 /usr/lib/java/jss4.jar /usr/lib64/jss /usr/lib64/jss/jss4.jar /usr/lib64/jss/libjss4.so /usr/share/doc/jss /usr/share/doc/jss/MPL-1.1.txt /usr/share/doc/jss/gpl.txt /usr/share/doc/jss/jss.html /usr/share/doc/jss/lgpl.txt $ rpm -ql ~/build/jss/RPMS/jss-debuginfo-4.* /usr/lib/debug /usr/lib/debug/.build-id /usr/lib/debug/.build-id/3f /usr/lib/debug/.build-id/3f/4af84b1095db43b47021b43ce3753c8a599041 /usr/lib/debug/.build-id/3f/4af84b1095db43b47021b43ce3753c8a599041.debug /usr/lib/debug/usr /usr/lib/debug/usr/lib64 /usr/lib/debug/usr/lib64/jss /usr/lib/debug/usr/lib64/jss/libjss4.so-4.5.0-1.fc28.x86_64.debug
Therefore, I'm marking this as not a bug because this is how the RPM+Debuginfo system is supposed to work. :) If you have additional questions, feel free to reopen/comment here.
Metadata Update from @cipherboy: - Issue close_status updated to: invalid - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.