On Wed, 2017-03-15 at 10:12 +0100, Remi Collet wrote: > Hi, > > It seems some recent changes (rawhide) result in tons of files in > /usr/lib/.build-id which are obviously not needed, and as non-unique > create conflicts > > ex: https://kojipkgs.fedoraproject.org/work/tasks/1239/18391239/root.log Thanks for the report and bug report. https://bugzilla.redhat.com/show_bug.cgi?id=1432372 The issue is not the files themselves but the directories they are in. The files got moved to a new location but obviously in a wrong way since previously the directories didn't conflict. I'll look into it. BTW. This is controlled by the following rpm macro: # # Defines how and if build_id links are generated for ELF files. # The following settings are supported: # # - none # No build_id links are generated. # # - alldebug # build_id links are generated only when the __debug_package global is # defined. This will generate build_id links in the -debuginfo package # for both the main file as /usr/lib/debug/.build-id/xx/yyy and for # the .debug file as /usr/lib/debug/.build-id/xx/yyy.debug. # This is the old style build_id links as generated by the original # find-debuginfo.sh script. # # - separate # build_id links are generate for all binary packages. If this is a # main package (the __debug_package global isn't set) then the # build_id link is generated as /usr/lib/.build-id/xx/yyy. If this is # a -debuginfo package (the __debug_package global is set) then the # build_id link is generated as /usr/lib/debug/.build-id/xx/yyy. # # - compat # Same as for "separate" but if the __debug_package global is set then # the -debuginfo package will have a compatibility link for the main # ELF /usr/lib/debug/.build-id/xx/yyy -> /usr/lib/.build-id/xx/yyy %_build_id_links compat So setting it to alldebug would give you the previous location. Cheers, Mark _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
