Conflicting build-ids in chromium and chromium-freeworld

[Marcin Zajączkowski]

Hi. There is an ongoing problem with conflicting build-ids in chromium
and chromium-freeworld [1][2]:
>  Error: Transaction test error:
>    file /usr/lib/.build-id/61/91aba223f60784c4a2fb95cdedcedc97217e5b from install of
> chromium-freeworld-85.0.4183.102-1.fc32.x86_64 conflicts with file from package
> chromium-85.0.4183.102-1.fc32.x86_64
>    file /usr/lib/.build-id/82/5827dc3adff19282b7b337b044b381e2f226ee from install of
> chromium-freeworld-85.0.4183.102-1.fc32.x86_64 conflicts with file from package
> chromium-85.0.4183.102-1.fc32.x86_64
>    file /usr/lib/.build-id/c1/a0a2a071572e46f4b3800bbb0f7ba217b42df7 from install of
> chromium-freeworld-85.0.4183.102-1.fc32.x86_64 conflicts with file from package
> chromium-85.0.4183.102-1.fc32.x86_64
>    file /usr/lib/.build-id/cc/2a382a1ab1ec74354adf012ad958a17f880f88 from install of
> chromium-freeworld-85.0.4183.102-1.fc32.x86_64 conflicts with file from package
> chromium-85.0.4183.102-1.fc32.x86_64
>    file /usr/lib/.build-id/d9/1c0feec7526201e135457e3a7f4ff4e4aebfea from install of
> chromium-freeworld-85.0.4183.102-1.fc32.x86_64 conflicts with file from package
> chromium-85.0.4183.102-1.fc32.x86_64 
There is no clear idea why it happens, but my assumption is that due to
the fact of building with the same source code (with similar patches),
some generated shared libraries are the same which generates conflict(s).

The quick look at the algorithm for build-id generation [3] doesn't
answer my question what exactly is taken into account for their
generation and more precisely is there is way to add some "fuzz" (having
different buildroots doesn't help) to distinguish those libraries.

To wrap up:
1. Is there a better way to deal with the aforementioned build-id
conflicts than disable their generation on one side (with "%global
_build_id_links none")?
2. Maybe my assumption about the same generated shared libraries is
wrong and there is something else what can be done to fix the root problem?


[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1869037
[2] - https://bugzilla.rpmfusion.org/show_bug.cgi?id=5743
[3] -
https://github.com/rpm-software-management/rpm/blob/505fe16f863f83637c957...
[4] - https://bugzilla.rpmfusion.org/show_bug.cgi?id=5758

Marcin

P.S. There are cases where it would be best to have those two packages
installed simultaneously [4].

-- 
https://blog.solidsoft.pl/ - Working code is not enough