Hello, On 2021-08-05 14:56, Stefan Seyfried wrote:
On 05.08.21 08:51, jsmeix wrote:
What I like to say is:
It makes sense to split one same piece of upstream software into parts so end-users don't have to install all of it and that parts should by default depend all on each other by exact RPM %{version}-%{release} to make the split maintainable with reasonable effort.
Still, the real problem here is, that libudev gained new functionality without its soversion being properly adjusted.
Every other piece of software could have fallen into the same trap.
I don't know the details of the changes in libudev here. Perhaps libudev also provides some "private things" that are only used by what is in the same tarball together with libudev so no other piece of "external" software would be affected? We had to learn that the hard way a long time ago because libcups also provides "private functions" that are only used by what is in the CUPS tarball but we did not have an exact RPM %{version}-%{release} dependency beween libcups and the other RPMs built from the CUPS tarball and once there was some libcups fix that let cupsd segfault because only libcups got updated but not all the rest of what we built from the CUPS tarball. Kind Regards Johannes Meixner -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5 - 90409 Nuernberg - Germany (HRB 36809, AG Nuernberg) GF: Felix Imendoerffer