Hi,

The libzstd package in testing is currently missing a couple of
build-time tests and a fix for a very rare data corruption bug.
Both of these have been fixed in libstd-1.5.4+dfsg2-5 in unstable;
however, I feel like I cannot ask for an unblock from the release
managers since the sparc64 buildd started failing on this package
at some point in February:

  https://buildd.debian.org/status/logs.php?pkg=libzstd&arch=sparc64

Now, the -1, -2, and -4 failures I can explain: there were some
problems in the upstream test suite that were fixed in -3 and -5.
However, -3 and -5 should really not have failed: they built
successfully on all other architectures where the build dependencies
were installable, and they also passed autopkgtest runs:

  https://ci.debian.net/packages/libz/libzstd/

I set up a qemu-based sbuild environment on my laptop, and
I built the libzstd package successfully. Is it possible that
something is wrong with the sparc64 buildd? Could somebody with
an actual sparc64 box try to build libstd-1.5.4+dfsg2-5 and
let me know if it works for them?

Thanks in advance!

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:        http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13

Attachment: signature.asc
Description: PGP signature

Reply via email to