Updating xbps itself will fail

[smorimoto]

I don't know if this only happens during clean install, but we get this error: https://github.com/am11/VoidWSL/pull/5/checks

[sgn]

Would you mind add verbose flag to xbps-install?

[Duncaen]

The error is at https://github.com/am11/VoidWSL/pull/5/checks#step:5:101 probably related to lib64 stuff.

[ericonr]

/bin/sh: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory

@smorimoto you need to be sure the /usr/lib64 -> /usr/lib symlink exists. It's created by base-files, so it should just be there, but idk. You could try force-reinstalling base-files.

[smorimoto]

All went well with 20210218: https://github.com/am11/VoidWSL/pull/5/checks

[Duncaen]

In general the pipeline step should try to update xbps itself first and then a full system update, since the current xbps version will not do a full update when a xbps update is available:

xbps-install -Suy xbps; xbps-install -Suy

[smorimoto]

I remember that when I tried that in a previous release, the environment was broken after xbps-install -Suy xbps.

[ericonr]

The previous images had a very unfortunate issue where they removed those symlinks for reasons unknown to mankind. Because we hacked glibc, it worked, but it was kind of accidental. The new images should have it all sorted out.

[smorimoto]

Oh, it's fine as long as it works with the latest release. Thanks!