Your message dated Mon, 08 Dec 2025 19:19:25 +0000
with message-id <[email protected]>
and subject line Bug#1119558: fixed in simka 1.5.3-10
has caused the Debian Bug report #1119558,
regarding simka: please build using the default build flags
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.)
--
1119558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119558
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: simka
Version: 1.5.3-9
User: [email protected]
Usertags: hardening-buildflags
simka is not currently using the default build flags set by dpkg-buildflags(1).
The default flags are chosen for multiple reasons including security,
performance, reproducibility, adherence to standards, and error handling.
Please make sure that simka builds using the default build flags. blhc(1p)
and hardening-check(1) can be used to confirm that the issue is fixed.
In the general case, packages honoring CFLAGS, LDFLAGS, and other
similar environment variables get the default build flags for free
without the need for any work on the maintainer side. In the case of
simka, the flags are either ignored or overridden.
The most common reasons for this are:
Hand-written Makefiles
----------------------
Some upstream Makefiles either override the values of variables such as
CFLAGS and similar or do not use them at all. See:
https://wiki.debian.org/HardeningWalkthrough#Handwritten_Makefiles
Misconfigured build systems
---------------------------
If the upstream code uses autotools, CMake, or other popular build
systems, it usually requires no further modifications. If might however
be that some variables are hardcoded in some way.
In this CMake snippet, the value of CXXFLAGS is overwritten with "-O2":
set(CMAKE_CXX_FLAGS "-O2")
If the intention is to append to CXXFLAGS, one should use the following
instead:
set(CMAKE_CXX_FLAGS "-O2 ${CMAKE_CXX_FLAGS}")
See #655870 for a similar autotools example.
Very old debhelper usage
------------------------
Packages not using dh(1), or those using a debhelper compatibility level
less than 9, need to manually include /usr/share/dpkg/buildflags.mk in
order for the dpkg-buildflags variables to be set:
https://wiki.debian.org/Hardening#dpkg-buildflags
Flags hardcoded in debian/rules (either voluntarily or not)
-----------------------------------------------------------
Some packages voluntarily hardcode the values of CFLAGS and friends in
debian/rules, ignoring the defaults set by dpkg-buildflags(1).
Others attempt to append to the variables, but end up accidentally
overriding the defaults:
#!/usr/bin/make -f
export CFLAGS += -pipe -fPIC -Wall
%:
dh $@
Debhelper only sets CFLAGS if it is not set yet. In the example above,
when dh is invoked the value of CFLAGS is "-pipe -fPIC -Wall", hence the
hardened defaults are not used. The right way to append to CFLAGS is
using DEB_CFLAGS_MAINT_APPEND instead, as documented in
dpkg-buildflags(1).
For a detailed analysis of this issue, see:
https://people.debian.org/~ema/nocflags_paper.pdf (eprint: hal-05334704)
--- End Message ---
--- Begin Message ---
Source: simka
Source-Version: 1.5.3-10
Done: Étienne Mollier <[email protected]>
We believe that the bug you reported is fixed in the latest version of
simka, 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.
Étienne Mollier <[email protected]> (supplier of updated simka 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: Mon, 08 Dec 2025 19:38:36 +0100
Source: simka
Architecture: source
Version: 1.5.3-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
<[email protected]>
Changed-By: Étienne Mollier <[email protected]>
Closes: 1119558
Changes:
simka (1.5.3-10) unstable; urgency=medium
.
* Team upload.
.
[ Andreas Tille ]
* Do not try to build for i386 in Salsa CI.
.
[ Étienne Mollier ]
* use_debian_packaged_libraries.patch: update.
The patch is adjusted to account for Debian default flags. Initial
version explicitly excluded system build flags but does not state why,
and the package proves to operate properly with the system flags.
(Closes: #1119558)
* detailed_errors.patch: unfuzz.
* fix_temp_arrays.patch: normalize dep3 header.
* d/control: drop redundant Rules-Requires-Root: no.
Checksums-Sha1:
e37722a330d8b1f84835a3cf8e16cc890e906a01 2348 simka_1.5.3-10.dsc
e0637437960c8e4fb104ff562b1bb3b259f14b22 22244 simka_1.5.3-10.debian.tar.xz
Checksums-Sha256:
e67155057f937768627c0136fd4cc8004a171c9c72581712e4734cba8d75867a 2348
simka_1.5.3-10.dsc
4e47bbe1cc41604c02bf0c47c3e25302e3ffff2c243e1b16321bed32a730fb9e 22244
simka_1.5.3-10.debian.tar.xz
Files:
4f218255d6d97a19daa2790fbdff2984 2348 science optional simka_1.5.3-10.dsc
96af6d16e710fc3d9542d2a30022ab42 22244 science optional
simka_1.5.3-10.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmk3H7UUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdrDPRAAwMJtaMhqGw/MpLCuh7ZNhMfiitiW
tZBBbj72q963Qdm1iYBJdd7/3EqNbZFw3BNuoi1W9kzaanIuVnSla/5jMzUqinMU
pyGU+ro0jBo+RDFcuEDxuNx60V2Ig0DylK6qEpfIyIajldGmmcCNAvn0CwUl6/di
5H8eCFBtMeUfjxVUX0Iyy6BQzlui78hxI4QzRjBE7BWkyr2R3cwzv6K6v6gRC+vc
E21kf9WMYjNxHP2eqcaVKe4A6xzQACqSYiG76xy3obQLXC5meNBMnwjeOiaeMTa0
AH+vae53tiHsDIioN784zKW3S/uV21LhyAu+hgbYznjQv82fojbxH7aon6CTDoY1
uE0d5IgyTUEj+eLbo7J4HAPinVfyPSS/Wlk1xbcjkjMOBTjB9Qf9lQFOjHC9Ozcy
uEUeu10XtV5+bGorUGiSO1xRHE1HeyNvsYUG8KaAoTGow9kEeVtS+xitM2eAbANM
VtxigHL7PZCZI61Th4F5AtwxJOzVEvudVNyvkKaEQ36P/CrEZXfnfvSxsZJcQUeb
qvuyGWyzBhqkK8AD13c0iM7qoZtvFIG+OJtLieJwj+VzCWJwMKyKS4NYa5ENYz2q
fxHFLpOz3SS85v+Id6XNXf7lTBUcnydtOC38hKalBlIN9lgWBUSc1J6kNvRyoEhI
gdbjre6iqhkHEOc=
=n/6U
-----END PGP SIGNATURE-----
pgpMci2RcmNeO.pgp
Description: PGP signature
--- End Message ---
