Your message dated Sun, 11 Feb 2024 21:52:32 +0000
with message-id <e1rzhkw-008agz...@fasolo.debian.org>
and subject line Bug#1061007: fixed in xeus 3.1.3-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
Source-Version: 3.1.3-2
Done: Gordon Ball <gor...@chronitis.net>

We believe that the bug you reported is fixed in the latest version of
xeus, 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 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:12:56 +0100
Source: xeus
Architecture: source
Version: 3.1.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Gordon Ball <gor...@chronitis.net>
Closes: 1060164 1061007
Changes:
 xeus (3.1.3-2) unstable; urgency=medium
 .
   * d/control: build-depend on nlohmann-json3-dev 3.11.3
     The API of this library exposes types from nlohmann::json, and this
     resulted in an ABI change depending on whether libxeus and the kernel
     are built against 3.11.2 or 3.11.3. This adds an explicit dependency
     on nlohmann-json3-dev 3.11.3. This explicitly chooses the newer version
     for libxeus and dependencies. (Closes: #1060164, #1061007)
Checksums-Sha1:
 84e6d12c132bd0b4bd58fd5c0b55bbcddddebdd3 2051 xeus_3.1.3-2.dsc
 fbb9dc1984258144995ff9c6974a22b6e622fd09 4536 xeus_3.1.3-2.debian.tar.xz
 374dd3346197b37ccdc0c461306a7d61fc37a80a 7758 xeus_3.1.3-2_amd64.buildinfo
Checksums-Sha256:
 85b6e3fa3fe0e6da29c0a4d7de5b1f9d5e031559c8d109d8f2d61b33af3cab12 2051 
xeus_3.1.3-2.dsc
 88369c874842ba98ba67cd26a74c67ceb10f452cfcf2427bd8cbe3773fe94253 4536 
xeus_3.1.3-2.debian.tar.xz
 311acbffd2c01da35a7753f1aa258a5fcefa10ba891569ab92b8f36a24a4f636 7758 
xeus_3.1.3-2_amd64.buildinfo
Files:
 9c5da1de704b8ded58398b8a348f315c 2051 libs optional xeus_3.1.3-2.dsc
 9f7d3f234d4c3fdb4175fa8a64b5e753 4536 libs optional xeus_3.1.3-2.debian.tar.xz
 51e658449f2ce09a46fcc334514674f1 7758 libs optional 
xeus_3.1.3-2_amd64.buildinfo

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

iQIzBAEBCgAdFiEE6PwpXIa418BJ+Xuno12v+60p6N4FAmXJPWQACgkQo12v+60p
6N7pvBAArF1GbiwFDjU7FQIWs1DAux3LYBC7ghwcpN9puImOUpBRyCzHZbEtkf1d
cpsOuWY7FYZFhEmQVfXtKY3eLWOLpTz+mBNrZCarEjUr7WgZtUBwk5Eza4sCf0ND
I5nF93aQ+k0DA5Ifr3RWH9hTthVlr/OwMVhIDHHc6q6CLO04VmzfCdNKi1FvgAsL
AzNxtawW9LDjBS1Fy/RaqqTx4sJ0VNfWJ45U9g0074YBmX2eqzlTWIIptKNxb3NN
/LIKXBbQkIPvee9cnM7loXjvqOGUoP0RY7C5PniI3KmnVBWKttrvyC1c9diro/Pg
JpE4mICiMfDNMs6ZDk9R7Ye0TccJU4JhxTjeCNk/Zxlrn0qaiVHuM3BBNIJf006x
Du5NyGYEeqsKsS6RIFdiOtm2s+owmfcIJlnAtiMkRSJdnXt9xp9DXni3E17Dumn9
rYB0RhpvHsDKelBdSdfffUrGWMVSjFCjGRTfAcju/OEaTbpjYle8ZAYCNJkjeJeM
jM1idweo9ijOn+SENw1mj1hA5HOKXfonK1NyuQ8VecN3pacWf5j8BnRVy2OznFl5
UTpzK29zaA5IbwMFxOJgQRe04TCs97t/G30I7CAKj/31+zy9f/QH7SUi6cbCHtox
C4I2IVxkK4BHTcJOltxtuuTDFeIv9oxjwgY1kOh1WycvoSpT4Hs=
=gFVb
-----END PGP SIGNATURE-----

Attachment: pgppu0pIw05rC.pgp
Description: PGP signature


--- End Message ---

Reply via email to