Package: android-libandroidfw Version: 1:14~beta1-2 Severity: serious User: [email protected] Usertags: time-t
Hi Umang, Analysis of the archive for the 64-bit time_t transition[0][1] identifies android-libandroidfw as a package shipping a library whose ABI changes on 32-bit architectures with 64-bit time_t. However, android-libandroidfw's shlibs file declares a dependency on a library package name that contains no ABI information: $ cat DEBIAN/shlibs libandroidfw 0 android-libandroidfw $ It is therefore not obvious that we should rename the package to 'android-libandroidfwt64' as part of this transition. Looking at the archive, there are packages that depend on this library, aapt and split-select. Despite being built from the same source package, they do not have a strict versioned dependency on android-libandroidfw but instead use the shlibs. 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-libandroidfw without also upgrading aapt, split-select) 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/ [email protected] [email protected] [0] https://wiki.debian.org/ReleaseGoals/64bit-time [1] https://lists.debian.org/debian-devel/2024/01/msg00041.html
signature.asc
Description: PGP signature
