Public bug reported: Please remove kallisto 0.51.1+dfsg-2 from stonking-proposed. 0.48.0+dfsg-4build2 stays in the release pocket.
0.51.1+dfsg-2 has been in proposed for 144 days, blocked by an autopkgtest regression in pizzly/0.37.3+ds-12 (amd64v3, arm64, ppc64el). With 0.51.1, kallisto segfaults in the quant step with fusion detection that pizzly's test uses: https://autopkgtest.ubuntu.com/results/autopkgtest-stonking/stonking/amd64v3/p/pizzly/20261011_090659_f7ead@/log.gz Quantifying using kallisto with fusion detection enabled ... Segmentation fault (core dumped) kallisto quant -i ... run-unit-test FAIL non-zero exit status 139 Upstream has an open report of the same problem: https://github.com/pachterlab/kallisto/issues/465 ('Quantifying abundances: Segmentation fault on all kallisto versions above 0.48.0'). Debian: kallisto was removed from testing because of RC bug https://bugs.debian.org/1118526 (heap corruption in the bundled bifrost code during the tests). That bug was filed against 0.48.0 and is still open, so it also keeps 0.51.1 out of testing. Keeping 0.48.0 in stonking avoids shipping a version that crashes pizzly's documented workflow. Nothing else in proposed needs 0.51.1. It will autosync again once Debian and upstream sort this out. ** Affects: kallisto (Ubuntu) Importance: Undecided Status: Fix Released ** Tags: stonking update-excuse ** Tags added: stonking update-excuse ** Changed in: kallisto (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2170936 Title: Please remove kallisto 0.51.1+dfsg-2 from stonking-proposed (segfaults in pizzly's fusion quant) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kallisto/+bug/2170936/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
