[sniper] libwayland-client0 ordered incorrectly vs. Debian 9
When we use pressure-vessel to run the in-development sniper runtime (based on Debian 11) on a Debian 9 host, libSDL2-2.0.so.0 can't be loaded:
[2021-09-10T13:15:46.436Z] "libSDL2-2.0.so.0" : {
[2021-09-10T13:15:46.436Z] "messages" : [
[2021-09-10T13:15:46.436Z] "Unable to find the library: /lib/x86_64-linux-gnu/libSDL2-2.0.so.0: undefined symbol: wl_proxy_get_tag"
[2021-09-10T13:15:46.436Z] ],
[2021-09-10T13:15:46.436Z] "soname" : null,
[2021-09-10T13:15:46.436Z] "path" : null,
[2021-09-10T13:15:46.436Z] "issues" : [
[2021-09-10T13:15:46.436Z] "cannot-load"
[2021-09-10T13:15:46.436Z] ],
[2021-09-10T13:15:46.436Z] "exit-status" : 1
[2021-09-10T13:15:46.436Z] },
The Debian 9 host has libwayland-client0_1.12.0-1+deb9u1
.
The Debian-11-based container has libwayland-client0_1.18.0-2~exp1.1
(sic).
Those are both libwayland-client.so.0.3.0
, so we can't decide which is newer, and end up using the one from the host, which is the wrong decision for a runtime as new as Debian 11.
The issue tracked as T23255 internally was a similar problem with soldier (Debian-10-based, with libwayland-client0_1.16.0-1
) running on brewmaster (Debian-8-based, with 1.15.0-2+bsos1
).
steamrt/steamrt#75 should have saved us from this, but perhaps that change needs forward-porting into sniper?
https://gitlab.freedesktop.org/wayland/wayland/-/issues/175 would be the long-term solution.