On Wed, Sep 8, 2021 at 10:25 AM Guillaume Gardet Guillaume.Gardet@arm.com wrote:
In Tumbleweed, we have libz-ng-compat1 which can be a drop-in replacement of libz1. The problem is zypper drop the previous package, before installing the new one, but the lib is required to extract the new RPM. Any idea how to solve this problem in the spec file?
sudo zypper in libz-ng-compat1 Loading repository data... Reading installed packages... Resolving package dependencies...
Problem: the to be installed libz-ng-compat1-2.0.5-1.1.aarch64 conflicts with 'libz1' provided by the installed libz1-1.2.11-18.10.aarch64 Solution 1: deinstallation of libz1-1.2.11-18.10.aarch64 Solution 2: do not install libz-ng-compat1-2.0.5-1.1.aarch64
Choose from above solutions by number or cancel [1/2/c/d/?] (c): 1 Resolving dependencies... Resolving package dependencies...
The following NEW package is going to be installed: libz-ng-compat1
The following package is going to be REMOVED: libz1
This is great ..however atm it is not a drop-in replacement.. on my development system...
The following 2 NEW packages are going to be installed: libz-ng-compat1 zlib-ng-compat-devel
The following 7 packages are going to be REMOVED: fontconfig-devel freetype2-devel gd-devel libpng16-compat-devel libpng16-devel libz1 zlib-devel
All those packages think they need zlib pkgconfig and are therefore uninstalled..now.. do they need zlib-devel ?..NO.. It is just a bunch of long standing , bloat-generating bugs. The most notorious one being pkgconfig still injecting Requires.private as hard dependencies even when there are no static libraries around. The result is that none of the above packages really need zlib headers around but it is installed anyway.