Your message dated Fri, 09 May 2025 17:49:00 +0000
with message-id <[email protected]>
and subject line Bug#1104994: fixed in mpdecimal 4.0.1-3
has caused the Debian Bug report #1104994,
regarding mpdecimal: Use LDXXFLAGS=$(LDFLAGS)
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.)
--
1104994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104994
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: mpdecimal
Version: 4.0.0-1
Severity: normal
X-Debbugs-Cc: [email protected]
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.9.10-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=C.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
Since there is only a single ./configure step for libmpdec and libmpdec++,
mpdecimal uses the non-standard LDXXFLAGS. (Unfortunately, without separate
LDXXFLAGS, it is not possible to specify -stdlib=libc++ for testing LLVM's
libc++.)
So, at some point LDXXFLAGS="$LDFLAGS" should be set, so that the C++ linker
also gets "-Wl,-z,relro -Wl,-z,now -Wl,--as-needed".
This will possibly get rid of the Lintian warning:
https://udd.debian.org/lintian-tag/hardening-no-relro
Stefan Krah
--- End Message ---
--- Begin Message ---
Source: mpdecimal
Source-Version: 4.0.1-3
Done: Ondřej Surý <[email protected]>
We believe that the bug you reported is fixed in the latest version of
mpdecimal, 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.
Ondřej Surý <[email protected]> (supplier of updated mpdecimal 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: SHA512
Format: 1.8
Date: Fri, 09 May 2025 19:28:02 +0200
Source: mpdecimal
Architecture: source
Version: 4.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Ondřej Surý <[email protected]>
Changed-By: Ondřej Surý <[email protected]>
Closes: 1104994
Changes:
mpdecimal (4.0.1-3) unstable; urgency=medium
.
* Export LDXXFLAGS to be same as LDFLAGS (Closes: #1104994)
Checksums-Sha1:
1d0747ff5dce6b9c240050ce0560b99d1f4087c6 2037 mpdecimal_4.0.1-3.dsc
0fa9ed13df032464b3962b86351084c2f25bb676 5360 mpdecimal_4.0.1-3.debian.tar.xz
f9bf96e690f48f8a864f5cb8ac125c69f5f68e7e 7478 mpdecimal_4.0.1-3_amd64.buildinfo
Checksums-Sha256:
99e04305c13ff470a964b507cec0dbe57f3d9f2452ddb8c76888af10382aced3 2037
mpdecimal_4.0.1-3.dsc
9424b078d45a7706eb4a4e66a86a4953777fbaf73f274b525dd20ac84b0078c3 5360
mpdecimal_4.0.1-3.debian.tar.xz
93c742a20d36f143691cbc971cb85c5dc6ecb0c70592a79533c96c61de545295 7478
mpdecimal_4.0.1-3_amd64.buildinfo
Files:
7a79b385b2504cbfac2252ef9dc88cfe 2037 libs optional mpdecimal_4.0.1-3.dsc
f942eb16ad4ebb3b79dbe29f3eec8015 5360 libs optional
mpdecimal_4.0.1-3.debian.tar.xz
a8a5ad20fc0e117fac25ec769ce5d1d1 7478 libs optional
mpdecimal_4.0.1-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmgeO2JfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcJ1/BAAqFkaFJ5ka4JDEYSOFpRg0gsGkejFZ4foZoQa4rBNUU5gIn7S5Ub3J/Hr
G1fcyL3uMvsOV4sFfZKcOJ7KDUBDHAyvtB3jNw0w9GRWQw6IwXlssbR54TcgHSVf
iVeoeBjwP/UbYtXh6hRFSTJYu0oaozQOeROMKg8hBij0aT4njK5gUR4kd+tfkLmA
HFgHg0YjM01fSbOWYUtYy+UqjRgUEguROatHFkusZnrhvXWBQhxHCjRBSU+NUaF4
4Du8c/AQM8l656hHbiTo63m4w1T8xHSgenXZk5jYvcFyTy5Bo/u+560QlupSxPgW
6FReabHtVXHFqsOwCyPOFn8gyg+5OO9yGB1WnzzmDfnC3XSbfo87Vsme99StzAsp
IfJd5XSLrpJUF2oneKm1ps4h3Vu/wC8+as5ksFhP86RQGWw4w9oC4f9tM7bxLSnF
mvzjfHmjRyD8oCPA5k7SePrlE9ZpeIeHJTvMCnYF3oGu4JSGP+pyB6D6VKjOXN+M
4Fup1b5YUDaKkdWXBu0zTlntj0r05HnZl1IOg+XoQldj2TP7h6HrwJe6no2MIYxL
YV1/Lzu4NGfpReXRLintEA/aO1CZw1QrXvFmuwsAHOnFQGM+vLqDsx6qrMXsJBvo
ZLW0f4lXbCdwlebLxFrJ60KBIHRqrUV3Q6Xl9LFzi3bHfszWZp4=
=M0Rx
-----END PGP SIGNATURE-----
pgphGk0YUtkMP.pgp
Description: PGP signature
--- End Message ---
