Hi, On Sun, 7 Apr 2019 16:46:01 +0200 Andreas Henriksson <andr...@fatal.se> wrote: > The lazy solution here is to argue that we don't want time-bombs and > just disable the test-suite. The better solution involves generating > the certificates so that they align with what 32bit machines can handle, > uuencoding the result and setting up debian/rules handling to "manually > patch" the build.
It has to be decided whether the issue, Debian-wise, is the FTBFS or the fact that heimdal does not properly handle dates beyond 2038 in 32 bit archs. I do not have hard data, but I believe that sometimes CAs set their expiration dates even decades in the future, so not verifying certificates expiring after 2038 might be an issue right now, and even more probably the buster's EOL. If we ignore this and just consider the bug as FTBFS, then it is easy to patch the package to that failing tests are ignored under 32 bit archs. Otherwise, the patch might be more complicated; I prodded upstream on the GitHub issue to understand their intentions. Giovanni. -- Giovanni Mascellani <g.mascell...@gmail.com> Postdoc researcher - Université Libre de Bruxelles
signature.asc
Description: OpenPGP digital signature
