Your message dated Thu, 20 Feb 2025 10:50:49 +0000
with message-id <[email protected]>
and subject line Bug#1091870: fixed in mfem 4.7+ds-3
has caused the Debian Bug report #1091870,
regarding libmfem4.7: Compile with MFEM_USE_EXCEPTIONS=YES
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.)
--
1091870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091870
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libmfem4.7
Version: 4.7+ds-2+b1
Severity: wishlist
Dear Alex Myczko,
Thank you for maintaining the package `mfem` in Debian. Is there a reason why
it is not compiled with
MFEM_USE_EXCEPTIONS=YES
Indeed, in this case, one still can request the program to be aborted on errors
with
mfem::set_error_action(ErrorAction::MFEM_ERROR_ABORT)
but one has the alternative of exceptions to handle problems.
Best,
Christophe
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (900, 'testing'), (400, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.6-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libmfem4.7 depends on:
ii libc6 2.40-4
ii libgcc-s1 14.2.0-8
ii libhypre-2.32.0 2.32.0-4
ii libmetis5 5.1.0.dfsg-7+b2
ii libopenmpi40 5.0.6-3
ii libstdc++6 14.2.0-8
libmfem4.7 recommends no packages.
libmfem4.7 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mfem
Source-Version: 4.7+ds-3
Done: Alex Myczko <[email protected]>
We believe that the bug you reported is fixed in the latest version of
mfem, 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.
Alex Myczko <[email protected]> (supplier of updated mfem 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: Thu, 20 Feb 2025 09:02:52 +0000
Source: mfem
Architecture: source
Version: 4.7+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Alex Myczko <[email protected]>
Changed-By: Alex Myczko <[email protected]>
Closes: 1091870
Changes:
mfem (4.7+ds-3) unstable; urgency=medium
.
* Use exceptions for build. (Closes: #1091870)
Checksums-Sha1:
badbecc1197cca925e10e9d0eda9e63ac37e3598 2031 mfem_4.7+ds-3.dsc
599e875eeee6234dceb90f2ab2056e895552cc8c 16248 mfem_4.7+ds-3.debian.tar.xz
e13054eeb5e29e432e4e1aca77d6e53abc150162 9824 mfem_4.7+ds-3_source.buildinfo
Checksums-Sha256:
1b9c8d0721ce3f6ddbfec2fe048f9c18490d4c0b101cd0648311b57f692fe974 2031
mfem_4.7+ds-3.dsc
f50c0f9a480ae122e1327ffbc775721da0963c64bcb5d52cbe7703636c1277c4 16248
mfem_4.7+ds-3.debian.tar.xz
7efdef1782aa4dde2da4057ddc824bdb2b4b5c942ace920f0c07b3dd97eb02aa 9824
mfem_4.7+ds-3_source.buildinfo
Files:
0003f901f7ac67be078c734edbeace34 2031 libs optional mfem_4.7+ds-3.dsc
508b49ea7bb5c3d148e4a909e297f49f 16248 libs optional
mfem_4.7+ds-3.debian.tar.xz
b05305ec5b64f78c19e909b0304cfe79 9824 libs optional
mfem_4.7+ds-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAme2/GAACgkQEWhSvN91
FcBNGBAAk4K4KhpALv5aGUHJ0ZN3JEBXJs2Ki403ZpnXYN8myux7/H1cAJUoUGQt
28ve29cSpojueD4/Y1dQg8z+WCn+tuNfQwfsOy9p0ukpRK7V1QFWAbQ0k8G+Gv4/
FjMvbDXzJyAW+4o5gjTH0RFJkCXdLaT5oNfEWQKFxaQ53OauasKBnf72nQeIbz1a
IWN1U6zA08raXq4DlN5n3FPJXz7ws6sknhoty6ECEJ/jq3v8jW2Dm3Zdox1ZERLi
n1WQVdXmLI3Tnl56yuzd02kgbJgHdq/9tGlqQAeU9mGkPco4+v2N+LuxL/scwekn
82RWhh0uBIaJT/I4WhkJnt4KKGY/Cge+FK7xlVRW5G5Ixu03E5oZ3lKOjgZCiJ42
GxD5mxPZEhH9QjnBz804RdUCwvg5ZBQ+wL48zDG9jN1qoHys2w9fijLMrw3Gr0EI
0rQ0XIjqcV40dKS8O7bV5XI1wc0HkuBrxRWwVrS2tCEyzRjC+LbJOBfDpeLzPFAX
SaU6hdbok3o8eeQVwBQZCagicyFM6UhLyz2GL4Xu7vvjcjkb4mZpvB46C6j7Uztl
cr9WHQT6v0Ay7xDkv52yEh0JP1so94SekdrsPAMX+owroNMnyR5i8KsihBR0lA07
v/4pnKKi9yg9Rd+D5xd5o0v47ZFiwONr0Ppiw8HxpzcGpizDq3M=
=/bcf
-----END PGP SIGNATURE-----
pgprQFS5U1iQs.pgp
Description: PGP signature
--- End Message ---
