[Debian-med-packaging] Bug#1018972: blasr autopkgtest regression with pbbam 2.1.0

[Steve Langasek]

Source: pbbam
Version: 2.1.0+dfsg-1
Severity: serious
Affects: blasr 5.3.5+dfsg-4
User: ubuntu-devel at lists.ubuntu.com
Usertags: origin-ubuntu kinetic

Hi Andreas,

blasr's autopkgtests fail on amd64 when blasr is rebuilt against pbbam
2.1.0:

[...]
autopkgtest [11:27:53]: test run-unit-test: [-----------------------
[INFO] 2022-08-28T11:27:53 [blasr] started.
[INFO] 2022-08-28T11:27:53 [blasr] ended.
[INFO] 2022-08-28T11:27:53 [blasr] started.
[INFO] 2022-08-28T11:27:53 [blasr] ended.
output: OK
md5sum: alignment.sam.check: FAILED
WARNING: 1 computed checksum did NOT match
autopkgtest [11:27:54]: test run-unit-test: -----------------------]
[...]

  (https://ci.debian.net/packages/b/blasr/unstable/amd64/)

Unfortunately, Debian's autopkgtest infrastructure does not appropriately
handle autopkgtests for binNMUs, which means this regression did not block
pbbam and the new blasr from entering testing.

I am not sure what the severity of this regression is, but since an
autopkgtest regression would normally block testing promotion, I have filed
this bug as 'serious'.  If it's determined that the impact on blasr doesn't
make blasr unreleasable, feel free to downgrade.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                   https://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/debian-med-packaging/attachments/20220902/0ef22a4d/attachment.sig>