verify shlib errors on partial upgrade bypassed by multilib
oreo639 opened this issue · comments
When performing shlib checks before upgrading, libraries provided by 32bit packages are treated the same as libraries provided by 64bit packages. This can result in system breakage on partial upgrades without warning as noticed on the r/voidlinux subreddit: https://www.reddit.com/r/voidlinux/comments/18r0swm/psa_libxcrypt_updates/
I verified this behavior using the following:
- Download testpkgs.zip
- Run
./setup.sh
- In the cloned void-packages repo run:
./xbps-src binary-bootstrap
./xbps-src -m masterdir-i686 binary-bootstrap i686
./xbps-src pkg libhelloworld
./xbps-src -m masterdir-i686 pkg libhelloworld
./xbps-src pkg test1
xi test1
- You can run
test1
and it will outputhello world 7
as expected. - After that, modify the libhelloworld package to not install libhelloworld.so.1 and build it as
version=2
(do not build the 32bit package with this change). - When doing
xi -u
, you will receive a shlibs error as expected.test1-1_1: broken, unresolvable shlib 'libhelloworld.so.1'
- Run
xi libhelloworld-32bit
- Now run
xi -u
again, you will not receive any warnings and the upgrade will proceed as normal. - Confirm the breakage of
test1
as running it now outputstest1: error while loading shared libraries: libhelloworld.so.1: cannot open shared object file: No such file or directory
Ideally, xbps should be able to detect that the libraries provided by 32bit packages are not applicable to 64bit applications and visa-versa.