Your message dated Tue, 03 Apr 2018 22:00:59 +0000
with message-id <e1f3tz9-0000dy...@fasolo.debian.org>
and subject line Bug#890400: fixed in libbpp-core 2.4.0-1
has caused the Debian Bug report #890400,
regarding libbpp-core3: ABI change without soname chenge
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
890400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: physamp
Version: 1.0.3-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic autopkgtest

Hi Maintainer

Since the upload of libbpp-core 2.3.2-1, physamp's autopkgtests have been failing [1] with the following error:

autopkgtest [03:46:54]: test run-unit-test: [-----------------------
bppalnoptim: symbol lookup error: bppalnoptim: undefined symbol: _ZN3bpp16ApplicationTools18getDoubleParameterERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt3mapIS6_S6_St4lessIS6_ESaISt4pairIS7_S6_EEEdS8_bi
autopkgtest [03:46:55]: test run-unit-test: -----------------------]
autopkgtest [03:46:55]: test run-unit-test: - - - - - - - - - - results - - - - - - - - - -
run-unit-test        FAIL non-zero exit status 127


It looks like a symbol was dropped and a transition is needed.

Regards
Graham


[1] https://ci.debian.net/packages/p/physamp/unstable/amd64/

--- End Message ---
--- Begin Message ---
Source: libbpp-core
Source-Version: 2.4.0-1

We believe that the bug you reported is fixed in the latest version of
libbpp-core, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 890...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille <ti...@debian.org> (supplier of updated libbpp-core package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 22 Mar 2018 10:02:38 +0100
Source: libbpp-core
Binary: libbpp-core-dev libbpp-core4
Architecture: source amd64
Version: 2.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 
<debian-med-packag...@lists.alioth.debian.org>
Changed-By: Andreas Tille <ti...@debian.org>
Description:
 libbpp-core-dev - Bio++ Core library development files
 libbpp-core4 - Bio++ Core library
Closes: 890400
Changes:
 libbpp-core (2.4.0-1) unstable; urgency=medium
 .
   [ Julien Dutheil ]
   * Version 2.4.0.
 .
   [ Andreas Tille ]
   * Bump soversion due to ABI change
     Closes: #890400
   * Add symbols file
Checksums-Sha1:
 99a4885db94078ab9a81d4a7c34bb551c5fd3773 2135 libbpp-core_2.4.0-1.dsc
 3b231e20ba1bcd13c7d311fdc61afa7ca74b18a5 361113 libbpp-core_2.4.0.orig.tar.gz
 6087770a49d9744ed24ed5f09d35bcd0ced5790a 26348 
libbpp-core_2.4.0-1.debian.tar.xz
 b96366528796c6de9f8229443975c34544361c1b 908482 
libbpp-core-dev_2.4.0-1_amd64.deb
 89265db61959b5ee641b882ad870f99561e18bdd 7959400 
libbpp-core4-dbgsym_2.4.0-1_amd64.deb
 e0f6525bd295f45156d3f7ea6ec0a9a6d80cb60e 605932 libbpp-core4_2.4.0-1_amd64.deb
 201e3b3bd79d5ebb34fee7ca9927c8058100dacb 7243 
libbpp-core_2.4.0-1_amd64.buildinfo
Checksums-Sha256:
 ed5c4157c3d2755eac1a26c305b34c4278a83cfd79032568386ae7088e123fb0 2135 
libbpp-core_2.4.0-1.dsc
 0ef950385d1cd199dc8614247a1972d38513720f4f1c08e903a04f304d3d4503 361113 
libbpp-core_2.4.0.orig.tar.gz
 3849c865899172fc2b872434ff486a4daa100f653a006adde51e91325b8a7074 26348 
libbpp-core_2.4.0-1.debian.tar.xz
 24c0e12548e7674f9d2fa386d2f91e44fb06584412c32b52e51cfa8f9cfbdf46 908482 
libbpp-core-dev_2.4.0-1_amd64.deb
 540f98ec3f6902aa49b9d7c4223395f5ed688a202810fb9c9ea816aff923be5d 7959400 
libbpp-core4-dbgsym_2.4.0-1_amd64.deb
 f769d54e41336fbe99b0885ac19cd2293b33bb34c33a4b8b36d054275869fdca 605932 
libbpp-core4_2.4.0-1_amd64.deb
 c9796c7ced23616d2cb2bcabcc008104b7ccde07a930af632b3d813d6e49725f 7243 
libbpp-core_2.4.0-1_amd64.buildinfo
Files:
 3c4913f0425b40cf6c44eda4598837d6 2135 science optional libbpp-core_2.4.0-1.dsc
 791aa8e405a0b199b60528a9a3b0ea62 361113 science optional 
libbpp-core_2.4.0.orig.tar.gz
 77377224ac5300d3a554462ab3972cb3 26348 science optional 
libbpp-core_2.4.0-1.debian.tar.xz
 7c85a6043e9f06ca8e7331affd24eb90 908482 libdevel optional 
libbpp-core-dev_2.4.0-1_amd64.deb
 de8798abbfe0126efe9428ad7e2522cf 7959400 debug optional 
libbpp-core4-dbgsym_2.4.0-1_amd64.deb
 980d88b0ba734856f0f561f5b51b3971 605932 libs optional 
libbpp-core4_2.4.0-1_amd64.deb
 816ace70ba942cb4d01d0a24b55cab83 7243 science optional 
libbpp-core_2.4.0-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlqzclcRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFTQQ//WAo2TImDxBjiBrAHXPO/kAmKZpPf2Ixv
oP+ow5Kf3nDtzWfhWoHkgeui75CWCa8xJPnW/zIzgikg1Wr5hXfIHgDSeP/iKz9P
w9BcgeXuxyn/fmHCTst62dsehUCVdZtjuwrWxdkvoqXXc0iqlRhydvH602HN6MzV
t5JQ+KHY+De+1qfsj7yjsV9y/du28ICAashsCwKLD/Df1nlIuTsDau+ZCXNw+ZWc
BjgnTBjEOTPir/ofWUzTrbIgw3cmuQc7XXEicN2mJ4VIgF99IW2ADHEEjXUx/NLy
MhKy+1GEaIp1pTamGBLEVK7JlIPmLUGW1LsCYuU/azdyAauVbHA223xAIaKv9YJQ
V8Nv8Xv+Xq9m/A391/Q5jQfj2J7OARubkhTp+xgWPnyAe9XnpwUCf99C2a14w198
hYq8PGhvgVLG0pEoQ6SlsS+0FzhnENRx7I8HhRg8Ae5dyE95Car1y9XAZcnhfw3Q
3kchoi1fIKKH960cpQRJXpKbjQZ4rHDxCIKphNIj66BwTCQ8JKyvGVGbIz2FitnJ
3X9O+E08DP+siWlO7Q25aJLgnDsm/+RcqV/11g2Gi7ZlfWJQSzq7C7YlXmT6mpIl
zVEXdxdLp7o5ONVlHNaNqBfdwvzmy8SE2nO6hIMFVIj9lBqh5PCHSoC8zgVrKVCL
FUv83hxfbsU=
=DxSS
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to