El 24/5/25 a las 19:42, Bill Allombert escribió:
nlohmann-json3-dev has a well-known upstream bug that causes it to breaks the ABI with each minor version, see for example: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) -- Gordon Ball <gor...@chronitis.net> Sun, 11 Feb 2024 22:12:56 +0100 Unfortunately Gianfranco uploaded a new minor version of nlohmann-json3-dev during the freeze, hence breaking unstable. I suppose the other xeus packages have the same bug. %rmadison nlohmann-json3-dev nlohmann-json3-dev | 3.5.0-0.1 | oldoldstable | all nlohmann-json3-dev | 3.7.0-2~bpo10+1 | buster-backports | all nlohmann-json3-dev | 3.9.1-1 | oldstable | all nlohmann-json3-dev | 3.11.2-2 | stable | all nlohmann-json3-dev | 3.11.3-2.1 | testing | all nlohmann-json3-dev | 3.12.0-1 | unstable | all So I am unsure what to do. How are we supposed to deal with RC bug in unstable that do not affect stable ?
I am also unsure about what to do. Gianfranco, can you please comment on this? Note that the three bugs against xeus-* which I reported today are the only ones of this type which I found after building all packages in unstable, so adapting to the new nlohmann would not be a very bad option. [ But someone should probably talk with Release Managers and explain this, as I am just a bug reporter... ] Thanks.
