Hi Andy, On Fri, 2020-11-13 at 02:16 +0000, Andy Li wrote: > Re. https://bugzilla.redhat.com/show_bug.cgi?id=1896901 > > Since haxe-4.1.3-4 and nekovm-2.3.0-4, both nekovm and haxe packages > contains "/usr/lib/.build- > id/b0/aed4ddf2d45372bcc79d5e95d2834f5045c09c". > The nekovm one is a symlink to "/usr/bin/neko". The haxe one to > "/usr/bin/haxelib". > Both the neko and haxelib binaries are built with libneko, with a > nearly identical main.c with the only difference of the present of > neko bytecode embedded as a byte array (neko: the byte array is null; > haxelib: the byte array is the haxelib neko bytecode). > > I'm not sure how to resolve it. > Please advice. In general this (should) only happen if the binaries are really identical (e.g. when one of the packages build requires the other, but instead of linking/rebuilding some sources it simply copies a binary directly). The build-id is (also) derived from the full nvra. So really cannot be identical even if the sources are. But this relies on the binaries being build with debuginfo. So maybe some code isn't build with -g? Cheers, Mark _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
