notfound 1127743 zlib/1:1.3.dfsg+really1.3.1-2 kthxbye On Thu, Feb 12, 2026 at 02:13:11PM +0100, Paul Gevers wrote:
> With a recent upload of zlib the autopkgtest of google-android-installers > fails in testing when that autopkgtest is run with the binary packages of > zlib from unstable. It passes when run with only packages from testing. In > tabular form: > pass fail > zlib from testing 1:1.3.dfsg+really1.3.1-2 > google-android-installers from testing 1755725555-1 > all others from testing from testing > I copied some of the output at the bottom of this report. > Currently this regression is blocking the migration of zlib to testing [1]. > Due to the nature of this issue, I filed this bug report against both > packages. Can you please investigate the situation and reassign the bug to > the right package? ... > 131s /usr/lib/android-sdk/build-tools/19.1.0/aapt: error while loading > shared libraries: libz.so.1: wrong ELF class: ELFCLASS64 > 131s autopkgtest [03:13:03]: test command1 This looks like something in whatever the proprietary binaries are doing, and if the package were so misbuilt that the ELF headers were so mangled as to prevent loading I'd expect to see vastly more reports of problems than just one random CI failure like this. My best guess would be that some toolchain change has triggered some fragility in the non free code. I've untagged zlib for now, if there's some analysis showing an actual problem in the package feel free to retag it.
signature.asc
Description: PGP signature
