Re: Help with a libzstd sparc64 FTBFS on the buildd
On Thu, Apr 06, 2023 at 05:01:07PM +0200, Paul Gevers wrote: > Hi Peter, > > On 06-04-2023 15:37, Peter Pentchev wrote: > > 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: > > sparc64 is not a release architecture. sparc64 will not be better or worse > if something migrates. I suggest to consider those problem separately. TBH, that was my own understanding, and I was about to send an unblock request earlier today, but then I decided to take another look at the freeze policy and the phrase "migration for packages only allowed if all their binary packages have been built on buildds" threw me a bit. But yeah, I should have realized that should only apply to release architectures... thanks for correcting my thinking! 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 signature.asc Description: PGP signature
Re: Help with a libzstd sparc64 FTBFS on the buildd
Hi Peter, On 06-04-2023 15:37, Peter Pentchev wrote: 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: sparc64 is not a release architecture. sparc64 will not be better or worse if something migrates. I suggest to consider those problem separately. Paul OpenPGP_signature Description: OpenPGP digital signature
Re: Help with a libzstd sparc64 FTBFS on the buildd
On Thu, Apr 06, 2023 at 04:37:16PM +0300, Peter Pentchev wrote: > 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; ...of course this should have been libzstd-1.5.4+dfsg2-5 > 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=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? ...and of course this should also have been libzstd-1.5.4+dfsg2-5 > 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 signature.asc Description: PGP signature
Help with a libzstd sparc64 FTBFS on the buildd
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=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 signature.asc Description: PGP signature
