On 11. 02. 21 8:39, Lumír Balhar wrote:
Hello.
I'm facing a problem with a conflict between two packages from non-fedora
repositories. I'm using vscodium and rememberthemilk apps for a long time but
now I cannot update both because there is a conflict in /usr/lib/.build-id/.
Error: Transaction test error:
file /usr/lib/.build-id/14/512ca58e91f1940ba8e68d620c03e13cfb7d82 from
install of codium-1.53.1-1612917076.el7.x86_64 conflicts with file from package
rememberthemilk-1.3.2-1.x86_64
file /usr/lib/.build-id/1c/1eccea7fe32b13593eb32f999fc3ce90432239 from
install of codium-1.53.1-1612917076.el7.x86_64 conflicts with file from package
rememberthemilk-1.3.2-1.x86_64
file /usr/lib/.build-id/63/e57a96064e30d496ce9596cb5861ce64f52160 from
install of codium-1.53.1-1612917076.el7.x86_64 conflicts with file from package
rememberthemilk-1.3.2-1.x86_64
file /usr/lib/.build-id/66/c77539c4ab0def65c2f355188fe71bff7b602d from
install of codium-1.53.1-1612917076.el7.x86_64 conflicts with file from package
rememberthemilk-1.3.2-1.x86_64
file /usr/lib/.build-id/74/589964965a9efc95d3e4202f7fc6a7226b6e78 from
install of codium-1.53.1-1612917076.el7.x86_64 conflicts with file from package
rememberthemilk-1.3.2-1.x86_64
file /usr/lib/.build-id/76/90a7dcb40a4a052fdfb0f46a0dbeabbdf6df47 from
install of codium-1.53.1-1612917076.el7.x86_64 conflicts with file from package
rememberthemilk-1.3.2-1.x86_64
file /usr/lib/.build-id/a7/97d3b4a5fac6864fda3d230e3ac9104d624990 from
install of codium-1.53.1-1612917076.el7.x86_64 conflicts with file from package
rememberthemilk-1.3.2-1.x86_64
It seems to me that both apps are using the same engine which might lead to this.
Is it possible that both packages ship identical pre-compiled binaries (ELFs),
e.g. by bundling the "same engine" you mention?
The build-id files are links to the affected files, which should give you a hint.
$ rpm -qlvp codium-1.53.1-1612917076.el7.x86_64.rpm | grep <conflicting_hash>
$ rpm -qlvp rememberthemilk-1.3.2-1.x86_64.rpm | grep <conflicting_hash>
Is there any way how to solve this problem from user perespective?
You could unpack the RPM, delete the build-id files and repack it. That is, if
you have no power over the build
If you have even a slightest úpwer over the build process (even by filing
tickets), suggest to disable the generation of build-ids (I don't recall how
exactly).
See
https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/thread/436G5ITF4T7UMMWIDT6HIW6QUNLXD4AK/
See
https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/thread/GV2GKNX5RUYXNOTPHPH6AE3NNJDUXFP2/
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
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
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
