On Fri, Feb 02, 2024 at 08:21:57AM -0800, Steve Langasek wrote: > Dear developers, > > As mentioned previously on debian-devel[6], we know that there are a number > of library packages being included in this transition which we have not > proven have an ABI affected by 64-bit time_t. This is because the > engineering cost of analyzing the long tail of packages whose headers > out-of-the-box fail ABI analysis under abi-compliance-checker is much higher > than the cost of just changing the package name and moving forward with > rebuilds.
Why not use reproducible build on a 32bit platform and see whether the new library is different from the old one ? Do the libxxxt64 in experimental supposed to use the new ABI ? Because it does not seem to be always the case. Is there a lintian test for that ? Relying on dpkg-buildflags alone cannot be sufficient. Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here.
