Hi, Sorry for jumping into this topic.
Is there anything I can do to push for updates to this package? Becasue the package blocked debci team to create riscv64/testing chroot on our riscv64 workers due to this FTBFS on mips64el lead to fail to migrate. On Mon, Aug 12, 2024 at 10:33:28AM +0200, Aurelien Jarno wrote:
Hi,
...
But for upstream, it just hides the real bug. On those architectures, the NaN encoding is indeed different, but the resulted encoded data should be the identical, as defined in the RFC. Therefore I believe the real fix is to convert NaNs (and probably also infinities) during the encoding process.
My initial thoughts is to report this to upstream and then we can disable/skip NaNs related test on Debian side. But I am not sure if this is appropriate so let me make sure first here. BR, Bo
signature.asc
Description: PGP signature
