Am 31.01.24 um 17:07 schrieb Felix Salfelder:
On Wed, Jan 31, 2024 at 03:36:36PM +0000, Lukas Märdian wrote:
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
gnucap as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
Dear Lukas.
Thanks for your work.
I'm very certain that we do not use time_t anywhere. Certainly not
explicitly, and there is no time_t mentioned in any library interface,
leave alone header file.
Hence I believe this is a false positive. To remain on the safe side,
i'm happy to investigate the assessment if needed. Feel free to provide
any log files or evidence from the analysis.
Hi Felix!
Thank you for reaching out. Checking our latest abi-compliance-checker analysis
logs [1] shows that your package might indeed be a false positive. It failed to
analyze and therefore was included in our list, just to be on the safe side.
If you're sure that gnucap would not be affected you can ignore the NMU and
close this bug report.
-- Lukas
[1]
https://adrien.dcln.fr/misc/armhf-time_t/2024-02-01T09%3A53%3A00/logs/gnucap-common/base/log.txt
