Good day, I think my changes are ready for upload of libmaus2 2.0.766. The main change, in addition to the new upstream version, is the support for libsecrecy encrypted files; I almost forgot to add it before upload, since German added a check for libsecrecy support in configure.ac. :) Changes are available on Salsa: Étienne Mollier, on 2020-11-12 23:12:00 +0100: > Andreas Tille, on 2020-11-12 18:35:28 +0100: > > On Thu, Nov 12, 2020 at 05:45:44PM +0100, Étienne Mollier wrote: > > > > > > https://salsa.debian.org/med-team/libmaus2 > > > > > > I'm still running additionnal builds to catch eventual > > > regressions on arm64 and ppc64el, just in case. > > > > Very cool. Please let us know the result. No changes in the build and test results on my end: > The build and build-time tests targeting arm64 went quite well. > The build went well on ppc64el, but build-time test crashed on > testdnarank.sh and testRank.sh at the same steps as riscv64[1], > itanium[2] and mips64el[3] (that is, "testing CacheLineRank" and > "running short tests", respectively). > > [1] https://buildd.debian.org/status/fetch.php?pkg=libmaus2&arch=riscv64&ver=2.0.743%2Bdfsg-1&stamp=1598631353&raw=0 > [2] https://buildd.debian.org/status/fetch.php?pkg=libmaus2&arch=ia64&ver=2.0.743%2Bdfsg-1&stamp=1598627935&raw=0 > [3] https://buildd.debian.org/status/fetch.php?pkg=libmaus2&arch=mips64el&ver=2.0.743%2Bdfsg-1&stamp=1598625102&raw=0 > > There is one difference though, the test now crashes with a > segmentation fault, instead of a full report with a backtrace: > > [V] testing CacheLineRank: > qemu: uncaught target signal 11 (Segmentation fault) - core dumped > ./testRank.sh: line 7: 474960 Segmentation fault ../src/testRank > Exiting with return code 139 > FAIL testRank.sh (exit status: 139) > [...] > [V] running short tests... > qemu: uncaught target signal 11 (Segmentation fault) - core dumped > ./testdnarank.sh: line 7: 474972 Segmentation fault ../src/testdnarank > Exiting with return code 139 > FAIL testdnarank.sh (exit status: 139) > > At least, the build on i386 went through, so there are chances > #934619 can be addressed with a new update at least. I started > an armhf build just to see... I have not closed #934619. Build works on i386, but armhf still fails on my end, and Helmut was mentioning explicitely armhf. Please review, and upload or grand upload permissions. Kind Regards, -- Étienne Mollier <etienne.mollier@mailoo.org> Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/4, please excuse my verbosity.
Attachment:
signature.asc
Description: PGP signature