Source: pbcopper, pbbam Control: found -1 pbcopper/1.4.0+dfsg-1 Control: found -1 pbbam/1.0.6+dfsg-2 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of pbcopper the autopkgtest of pbbam fails in
testing when that autopkgtest is run with the binary packages of
pbcopper from unstable. It passes when run with only packages from
testing. In tabular form:
pass fail
pbcopper from testing 1.4.0+dfsg-1
pbbam from testing 1.0.6+dfsg-2
all others from testing from testing
I copied some of the output at the bottom of this report. To be honest,
this looks a bit messy. 1) libpbcopper.so.1.4.0 is shipped by a package
called libpbcopper1.3.0 (this may be correct, but very confusing; didn't
investigate further). 2) pbmerge is opening libpbcopper.so.1.3.0 instead
of something like libpbcopper.so.1 (and following symlinks). This may be
correct (again, I didn't investigate), but it makes updates to pbcopper
very fragile (as in this case) and isn't what normally happens with
libraries, where the symlinks make it possible to update the package
without rebuilding if SONAME compatibility is maintained, and otherwise
trigger a transition that can be handled by the release team.
Currently this regression is blocking the migration of pbcopper to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=pbcopper
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pbbam/5248083/log.gz
$ $PBMERGE $HQREGION_BAM $SCRAPS_BAM > $MERGED_BAM
+ pbmerge: error while loading shared libraries: libpbcopper.so.1.3.0:
cannot open shared object file: No such file or directory
+ [127]
signature.asc
Description: OpenPGP digital signature
