Something went wrong with the last run in builders:
=> Registering new packages to /host/binpkgs/multilib (x86_64)
index: failed to read props.plist metadata for `/host/binpkgs/multilib/libglapi-32bit-21.0.3_1.x86_64.xbps', skipping!
index: failed to read props.plist metadata for `/host/binpkgs/multilib/libgbm-32bit-21.0.3_1.x86_64.xbps', skipping!
index: failed to read props.plist metadata for `/host/binpkgs/multilib/libOSMesa-32bit-21.0.3_1.x86_64.xbps', skipping! index: failed to read props.plist metadata for `/host/binpkgs/multilib/mesa-vulkan-radeon-32bit-21.0.3_1.x86_64.xbps', skipping!
index: failed to read props.plist metadata for `/host/binpkgs/multilib/mesa-ati-dri-32bit-21.0.3_1.x86_64.xbps', skipping!
index: failed to read props.plist metadata for `/host/binpkgs/multilib/mesa-vulkan-intel-32bit-21.0.3_1.x86_64.xbps', skipping!
index: failed to read props.plist metadata for `/host/binpkgs/multilib/mesa-intel-dri-32bit-21.0.3_1.x86_64.xbps', skipping!
index: failed to read props.plist metadata for `/host/binpkgs/multilib/mesa-nouveau-dri-32bit-21.0.3_1.x86_64.xbps', skipping!
index: failed to read props.plist metadata for `/host/binpkgs/multilib/libxatracker-32bit-21.0.3_1.x86_64.xbps', skipping!
index: added `MesaLib-devel-32bit-21.0.3_1' (x86_64).
index: added `mesa-32bit-21.0.3_1' (x86_64).
index: added `mesa-XvMC-32bit-21.0.3_1' (x86_64).
index: added `mesa-dri-32bit-21.0.3_1' (x86_64).
index: added `mesa-opencl-32bit-21.0.3_1' (x86_64).
index: added `mesa-vaapi-32bit-21.0.3_1' (x86_64).
index: added `mesa-vdpau-32bit-21.0.3_1' (x86_64).
index: added `mesa-vmwgfx-dri-32bit-21.0.3_1' (x86_64).
index: added `mesa-vulkan-overlay-layer-32bit-21.0.3_1' (x86_64).
Since this didn't happen during local testing or on CI, a revbump should
hopefully be enough.
INSTALL script installed a /usr/lib32 symlink to /usr/lib on x86
machines (added in 5bb3a0cf7b), which has
been unnecessary for a long time, given that base-files contains the
symlink already. It was also the wrong solution: libdir being special
cased to /usr/lib32 on i686 (to provide the multilib repo) should have
led to the symlink being part of some base package, not a workaround in
a specific package.
Furthermore, ever since 488edb2a9c, the
package follows Void's policy of always using /usr/lib$wordsize as
libdir, instead of /usr/lib, and most things dealing with library paths
shouldn't be package specific.
---
Since we are here:
INSTALL.msg doesn't need to be printed every time the package is
updated, so move to README.voidlinux.
Don't use -f in rm commands.
