Hi,

thanks for taking care of precise symbols for xz-utils. Unfortunately,
this breaks bootstrapping musl-linux-any. Can musl be exempted here?

xz-utils uses symbol versioning, which is good. Unfortunately, musl (and
other non-glibc C libraries) does not provide the infrastructure for
symbol versioning in its dynamic linker. It is a feature that cannot be
used with musl. This completely breaks package upgrades the way Debian
does, but we can still build packages for a musl system from scratch and
assemble an OS image from there. Then image-based upgrades can work.

In any case, the xz-utils symbols do not reflect what xz-utils actually
provides on musl (and other non-glibc) architectures. I argue strict
symbol checking does not make sense there. The current musl bootstrap
simply exports DPKG_GENSYMBOLS_CHECK_LEVEL=0 and acknowledges that
package upgrades do not work. The code in xz-utils breaks this opt-out.

How abot matching linux+glibc here? I think that would be practically
good enough for what you wanted. Patch attached.

Helmut

Hi!

Thanks for the patch and yes, we can relax the symbols tracking for musl.

Are all your builds local or can you share links to the builds that started
failing for context?

Hi Otto,

Most of my builds are on https://jenkins.debian.net/view/rebootstrap/.
In particular, this became aparent on musl-linux-arm64 recently.

Helmut