Your message dated Tue, 29 Aug 2023 09:50:17 +0000
with message-id <[email protected]>
and subject line Bug#1050225: fixed in hypre 2.28.0-7
has caused the Debian Bug report #1050225,
regarding hypre: FTBFS: need relaxed tolerance on riscv64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1050225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050225
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: hypre
Version: 2.28.0-6
Severity: important
Tags: patch ftbfs
User: [email protected]
Usertags: riscv64
X-Debbugs-Cc: [email protected]

Dear maintainer,

hypre fails to build from source on riscv64 with error in the testsuite:
https://buildd.debian.org/status/fetch.php?pkg=hypre&arch=riscv64&ver=2.28.0-6&stamp=1691634845&raw=0

After investigation, it appears that riscv64 also needs to get the test
tolerance relaxed like on a few other architectures. I have tested that
this patch enables the testsuite to pass and the package to build
successfully:

--- hypre-2.28.0/debian/rules
+++ hypre-2.28.0/debian/rules
@@ -186,7 +186,7 @@
 
 # Standard tolerance 1e-6 is too tight on many arches
 # so relax them to 1e-3
-ARCH_RELAX_TOL_LIST = arm64 i386 ppc64el s390x hppa powerpc ppc64
+ARCH_RELAX_TOL_LIST = arm64 i386 ppc64el riscv64 s390x hppa powerpc ppc64
 
 ifneq (,$(findstring $(space)$(DEB_HOST_ARCH)$(space), 
$(space)$(ARCH_RELAX_TOL_LIST)$(space)))
   RELAX_TOL = HYPRE_CHECKPAR_TOL=1e-3


Would it be possible to include it in the next upload? Thanks in
advance.

Regards
Aurelien

--- End Message ---
--- Begin Message ---
Source: hypre
Source-Version: 2.28.0-7
Done: Drew Parsons <[email protected]>

We believe that the bug you reported is fixed in the latest version of
hypre, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Drew Parsons <[email protected]> (supplier of updated hypre package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 29 Aug 2023 10:26:33 +0200
Source: hypre
Architecture: source
Version: 2.28.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 
<[email protected]>
Changed-By: Drew Parsons <[email protected]>
Closes: 1050225
Changes:
 hypre (2.28.0-7) unstable; urgency=medium
 .
   * Team upload.
   * run build-time tests (make check) on ppc64el, only skip checkpar.
     Likewise with hurd-i386.
   * relax checkpar tolerance on riscv64. Closes: #1050225
   * report number of available processors (nproc) when running tests
     (hanging tests is more likely when oversubscribing)
Checksums-Sha1:
 fdd6a445eca826491c570488ef9a6891cd7e3cee 3436 hypre_2.28.0-7.dsc
 ec0407e74a0c5bc8c831b7e56fc8c2f13204cdf6 19552 hypre_2.28.0-7.debian.tar.xz
Checksums-Sha256:
 8b7b4305337a625c0da5a783e9ba9ed1c4bfee6e48f586cb5feeb925038ea255 3436 
hypre_2.28.0-7.dsc
 e1c679cb1f66d1eaf2ba246874c8574fac4154c3e410bf650c5e1327cf17e30b 19552 
hypre_2.28.0-7.debian.tar.xz
Files:
 3dd60ad69c4a6ea5178915a0c7a40aa9 3436 math optional hypre_2.28.0-7.dsc
 2c12812008134e76714db0f74044f1d0 19552 math optional 
hypre_2.28.0-7.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmTtt0wACgkQVz7x5L1a
Afq7mxAArZJq6M9ETEn48X4we+DxBCcayV/0zAoemjsCd3WzcLfCZu4aT5eS5Pt3
uwB5yvnScaZ4cQQfZrubJ/OdT8TFAk8H79LObzA2zDffv0o2Z/Tzm5NSfaBTadKI
5e8oKvKUEmfVozQ0cXqv/5VvXpUcsBCJ0toCP66U8VzT0XT9R88H0UnxXySVyHEk
wJ2zUxMrNlk184uPl0HAmaYCBkC2L2yQLCPY0FjY/2ANmTGw6M3rQn+uFfqF6wwm
eQGmPGuQmPv5C9qqqJdwTHCEdqbSWLsd7utbvyjBySeWaWjdsBbDxc78j5cxtbqO
gxDF3Jrs2BwOqTawbMutDNNiIY1/NtkTLrpyU2q8ispjz/o3FDsWYNpR6h2ZO7Dm
DaZBQpffJmXHF09VtJgJzC0p654aTFQXfgIWXlMHdaz7M63vyyuYjHonIakjvVTI
/LYtfMWz7UOqt5DcEBzIkwBQwJKMEWKuyreZyaR0m6VKaRp1Z9drywsk8tzmOc8M
bcyJkpqZKBrulhlyRA34Ow86fDCVjlaCPKjJvyA6f6z2lYss6LD0WoLd+7JteD84
k/7vm3dF2aitVOHD8oOLxOLRMwFqPP43QRx87z34nFsO4YvEgJ65soQCLYOOoai9
gQOp+UQICaQhZHkiuaC+j+YZtRSIUxOcmYslVfgo/tA9N9eMIcs=
=30UD
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to