Actions
Bug #11092
closedrdoc-generated *.gz files contain references to full path of the original, breaking rpmbuild
Description
Trying to build some RPMs here from GEMs I'm seeing the following complaint from rpmbuild-utility:
- /usr/lib/rpm/check-buildroot
Binary file /home/mi/rpmbuild/ti_ruby_gems/BUILDROOT/ti_ruby22-rubygem-rake-10.4.2-1.x86_64/data/packages/ti_ruby22/lib/ruby/gems/2.2.0/doc/rake-10.4.2/rdoc/js/search_index.js.gz matches
Binary file /home/mi/rpmbuild/ti_ruby_gems/BUILDROOT/ti_ruby22-rubygem-rake-10.4.2-1.x86_64/data/packages/ti_ruby22/lib/ruby/gems/2.2.0/doc/rake-10.4.2/rdoc/js/navigation.js.gz matches
Binary file /home/mi/rpmbuild/ti_ruby_gems/BUILDROOT/ti_ruby22-rubygem-rake-10.4.2-1.x86_64/data/packages/ti_ruby22/lib/ruby/gems/2.2.0/doc/rake-10.4.2/rdoc/js/searcher.js.gz matches
Found '/home/mi/rpmbuild/ti_ruby_gems/BUILDROOT/ti_ruby22-rubygem-rake-10.4.2-1.x86_64' in installed files; aborting
error: Bad exit status from /data/tmp/rpm-tmp.hv080f (%install)
Indeed, those three .js.gz all contain fill string referring to the location of the original (uncompressed) file.
Note, that the references are not inside the .js files -- but in the js.gz (likely inserted by zlib, when writing out gz-header). This should be fixed to avoid leaking the location of the originals, reduce occupied space, and, indeed, avoid freaking-out rpmbuild.
Actions
Like0
Like0Like0