Package: android-libbase Version: 1:34.0.4-1 Severity: serious User: debian-...@lists.debian.org Usertags: time-t
Hi Roger, Analysis of the archive for the 64-bit time_t transition[0][1] identifies android-libbase (and other libraries from android-platform-tools) as a package shipping a library whose ABI changes on 32-bit architectures with 64-bit time_t. However, android-libbase's shlibs file declares a dependency on a library package name that contains no ABI information: $ cat DEBIAN/shlibs libbase 0 android-libbase (>= 34.0.4) $ It is therefore not obvious that we should rename the package to 'android-libbaset64' as part of this transition, or to do similarly for the other libraries built from this source. Looking at the archive, there are packages built from both android-platform-tools and from separate source packages that depend on this library. Since there is no self-evident thing to do with the library package name here, we will not be handling this package as part of the mass NMUs. Instead I am filing a serious bug because partial upgrades from bookworm to trixie on 32-bit architectures (upgrading android-libbase without also upgrading adb, fastboot, dexdump, etc) will result in ABI skew and may result in broken behavior. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org [0] https://wiki.debian.org/ReleaseGoals/64bit-time [1] https://lists.debian.org/debian-devel/2024/01/msg00041.html
signature.asc
Description: PGP signature
