Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: transition X-Debbugs-Cc: abs...@packages.debian.org, Rene Engelhard <r...@debian.org> Control: affects -1 + src:abseil
Abseil 20230802 has been out for a while, and I'd like to transition sid to it. The new version has a new ABI (with a new SONAME and new binary package names). Tests for 20230802.1-2 in experimental are green on all supported architectures except mips64el and riscv64. mips64el had no installable libc when the builders ran; I expect it'll be fine when the transition actually happens. Large parts of Abseil (including the version already in sid) are broken on riscv64 right now because of https://bugs.debian.org/1059532; transitioning doesn't introduce any new issues. A number of packages in sid depend directly on Abseil. To give early warning of breakages, I've done trial rebuilds as appropriate on the amd64 porterbox. Packages that work fine with the new version: - grpc - libgav1 - libphonenumber - mujoco - open-vm-tools - ycmd Packages that are broken by the new version: - mozc: FTBFS because it depends on a symbol in the absl::internal namespace that changed without warning - re2: FTBFS because it needs changes to some symbols files - s2geometry: FTBFS because it hard-codes std=c+11 and the new version requires -std=c++14 or later (https://bugs.debian.org/1059228) - webrtc-audio-processing: FTBFS because it relies on transitive #includes that have changed Packages that I'm not sure about: - dm-tree: has an active FTBFS (https://bugs.debian.org/1055686) - ortools: has an active FTBFS (https://bugs.debian.org/1024790) - libreoffice: too big to build on a porterbox, so left untested Although doing a transition now will break some packages in sid, I believe waiting is likely to cause more issues. Upstreams (LibreOffice in particular) are starting to use features from the new version of Abseil, and keeping the old version in sid is starting to create work for other DDs. The breakages in sid will have to be fixed eventually anyway, and none of them should be challenging to repair. Ben file: title = "abseil"; is_affected = .depends ~ /\blibabsl20220623\b/ | .depends ~ /\blibabsl20230802\b/; is_good = .depends ~ /\blibabsl20230802\b/; is_bad = .depends ~ /\blibabsl20220623\b/;
