Re: [Rpm-ecosystem] why do elf dependency generators cover libraries in paths outside of the library load paths?

2021-12-03 Thread Dmitry V. Levin
On Fri, Dec 03, 2021 at 07:53:42PM +, Zbigniew Jędrzejewski-Szmek wrote: > We had an incident today [1] that opae-devel has auto-generated provides > like libcrypto.so.1.1()(64bit), generated for the bundled copy of openssl >

[Rpm-ecosystem] why do elf dependency generators cover libraries in paths outside of the library load paths?

2021-12-03 Thread Zbigniew Jędrzejewski-Szmek
We had an incident today [1] that opae-devel has auto-generated provides like libcrypto.so.1.1()(64bit), generated for the bundled copy of openssl (/usr/lib/python3.10/site-packages/pacsign/hsm_managers/openssl/library/libcrypto.so). It was pulled into the buildroot instead of the expected

Re: [Rpm-ecosystem] why do elf dependency generators cover libraries in paths outside of the library load paths?

2021-12-03 Thread Neal Gompa
On Fri, Dec 3, 2021 at 3:10 PM Miro Hrončok wrote: > > On 03. 12. 21 20:53, Zbigniew Jędrzejewski-Szmek wrote: > > We had an incident today [1] that opae-devel has auto-generated provides > > like libcrypto.so.1.1()(64bit), generated for the bundled copy of openssl > >