Your message dated Sun, 11 Feb 2024 21:52:40 +0000
with message-id <e1rzhke-008ajk...@fasolo.debian.org>
and subject line Bug#1061007: fixed in xeus-python 0.15.10+~0.6.1-2
has caused the Debian Bug report #1061007,
regarding libxeus9 incompatible with nlohmann::json_abi_v3_11_3
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.)
--
1061007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xeus-dev
Version: 3.1.3-1
Severity: serious
Dear Debian Science maintainers,
I have trouble with linking with libxeus9 since I upgraded
nlohmann-json3-dev to 3.11.3-1.
It seems to me nlohmann-json3-dev 3.11.3-1. is changing the API of libxeus9 in
an incompatible way.
/lib/x86_64-linux-gnu/libxeus.so.9 defines
xeus::make_null_debugger(xeus::xcontext&, xeus::xconfiguration const&,
std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >
const&, std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> > const&, nlohmann::json_abi_v3_11_2::basic_json<std::map,
std::vector, std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, bool, long, unsigned
long, double, std::allocator, nlohmann::json_abi_v3_11_2::adl_serializer,
std::vector<unsigned char, std::allocator<unsigned char> > > const&)
while programs compiled with xeus-dev and nlohmann-json3-dev require
xeus::make_null_debugger(xeus::xcontext&, xeus::xconfiguration const&,
std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >
const&, std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> > const&, nlohmann::json_abi_v3_11_3::basic_json<std::map,
std::vector, std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, bool, long, unsigned
long, double, std::allocator, nlohmann::json_abi_v3_11_3::adl_serializer,
std::vector<unsigned char, std::allocator<unsigned char> >, void> const&)'
That is 'nlohmann::json_abi_v3_11_3' instead of 'nlohmann::json_abi_v3_11_2'
This causes xeus-based kernels to fail to link.
main.cpp:(.text+0x58b): undefined reference to
`xeus::make_null_debugger(xeus::xcontext&, xeus::xconfiguration const&,
std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >
const&, std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> > const&, nlohmann::json_abi_v3_11_3::basic_json<std::map,
std::vector, std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, bool, long, unsigned long, double, std::allocator,
nlohmann::json_abi_v3_11_3::adl_serializer, std::vector<unsigned char,
std::allocator<unsigned char> >, void> const&)'
Downgrading nlohmann-json3-dev to 3.11.2-2 fixes this issue.
binNMUing libxeus9 might fix this issue, but will probably silently change the
ABI of libxeus9 without
updating the shlibs. This is worrysome. I hope I am wrong about that.
Cheers,
--
Bill. <ballo...@debian.org>
Imagine a large red swirl here.
--- End Message ---
--- Begin Message ---
Source: xeus-python
Source-Version: 0.15.10+~0.6.1-2
Done: Gordon Ball <gor...@chronitis.net>
We believe that the bug you reported is fixed in the latest version of
xeus-python, 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 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Gordon Ball <gor...@chronitis.net> (supplier of updated xeus-python 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: SHA512
Format: 1.8
Date: Sun, 11 Feb 2024 22:27:04 +0100
Source: xeus-python
Architecture: source
Version: 0.15.10+~0.6.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Gordon Ball <gor...@chronitis.net>
Closes: 1061007
Changes:
xeus-python (0.15.10+~0.6.1-2) unstable; urgency=medium
.
* d/control: build-depend on nlohmann-json3-dev 3.11.3, xeus-zmq 1.1.1-2;
this should resolve an ABI issue caused by xeus exposing nlohmann::json
(Closes: #1061007)
Checksums-Sha1:
500f44d166e966a51961aab55b0c527c8852c025 2898 xeus-python_0.15.10+~0.6.1-2.dsc
6bece6a3fe275e221367ffaa7c130d331514bd2a 9100
xeus-python_0.15.10+~0.6.1-2.debian.tar.xz
c723871df83563aad2104e38b987cf09797ec507 10602
xeus-python_0.15.10+~0.6.1-2_amd64.buildinfo
Checksums-Sha256:
613be6af8bd07b5834935421385c68979c1161f6a2dc306f249429dc5e8d1bd3 2898
xeus-python_0.15.10+~0.6.1-2.dsc
85ac6193b450ec739be0673fd2a466804943e89db94de07f6edb9afe15178003 9100
xeus-python_0.15.10+~0.6.1-2.debian.tar.xz
20ae5394454c34db62a15cdf3f5bdcc2e3d5aea6bf28ef4de049360be323bfd8 10602
xeus-python_0.15.10+~0.6.1-2_amd64.buildinfo
Files:
973e0101378dc56ab92f1ef8d91b651a 2898 science optional
xeus-python_0.15.10+~0.6.1-2.dsc
2df065a267a235848d09724f5c743a15 9100 science optional
xeus-python_0.15.10+~0.6.1-2.debian.tar.xz
0e85c934d7b0d855f97ae884cb0f39eb 10602 science optional
xeus-python_0.15.10+~0.6.1-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE6PwpXIa418BJ+Xuno12v+60p6N4FAmXJPWIACgkQo12v+60p
6N4VahAAqo++qeA8VDjSFd7ITYAhirUtWcXR8e0tslzpUBpj7bDCNTZNIbUDRiX9
9k7VotU74zDG6ZQ7nKZp0c5wjlT1fPsoWrs37YgUhwz5UZZwwZT7+hGC3K+CM+vr
opPhqWBMxCF3Z99gBi9ch369cgxeiiS68TnBB0FsENk31VFEokY6nVtA5ziB4WeI
0m8WErhUZ6uXsr9e2KnE9rhB+/gqd4YM/G8/q4BDAcQpfFzFibsKOSK1dRc7h6J0
/pjG4EVpp/pp05DO+NGynp7nyWbC/elXE13TWc2RuF5dU5f6pjHm5GFjTFIiVKFM
KxWsp7YRFXpQHsPQ7iZdXDC6IQ/FoOyeZleytE94lgDMJ3PhCqBfZGAJe8FXCLJF
wT+MteE+NmR8GD2rz0C+kX4i9fcxW9fbxthNBJLVwcVDav/2soTT12e6Lqu/3/rY
DquUHRAuujWfD3dYI/Eh4Pg9ZgURuf3vTk8dBKYxktZANffN7PgrDUIW/g9xxVoS
UaG3iEfk3pEkazo7DleBkMpMQxdGknQH/qVErMaBTPteu6R9Jp+BCbNt5UWGAC4x
nBdDrrkR+4ef8GErq6JQjHDIIFkvd92yMZo52rsj3kjljbezDxZN+fWVtVmaj8Dz
A1jnDt1ZOg+FPTDLpKHupSbxvnzCvDuZnKNkj/dI0yat2WFbMVs=
=Pkoy
-----END PGP SIGNATURE-----
pgpTkOAGe_iuG.pgp
Description: PGP signature
--- End Message ---
