[pkg-gnupg-maint] Bug#1063733: no -D_TIME_BITS=64 on builds where t64 support is supposed to be done

Rene Engelhard rene at debian.org
Sun Feb 11 21:10:56 GMT 2024


Source: gpgme1.0
Version: 1.18.0-4.1~exp1
Severity: important

[ let's no get into a discussion on  the sense of this transition. I 
actually believe this isn't needed and we can leave 32 bit die in 2038 
but anyways...

The transition is ongoing now in experimental. So be it ]


Hi,


I just tried a rebuild of libreoffice with 
DEB_HOST_MAINT_OPTIONS="abi=+time64" to actually see what happens.

It failed in a certificate unit tests so I tried to rebuild the 
"certificate" related (build-)dependencies also with 
DEB_HOST_MAINT_OPTIONS="abi=+time64"


While doing so I noticed that gpgme1.0 doesn't define -D_TIME_BITS=64 
even when built for t64 (as in the experimental NMU renaming to t64) on 
the affected architectures (anything 32-bit except i386).

This is probably because it doesn't honout dpkg-buildflags.

But even if you don't like dpkg-buildflags that define has to be done.

Regards,

Rene

P.S::
Thankfully libreoffice is fine without a rebuilt gpgme1.0 somehow



More information about the pkg-gnupg-maint mailing list