Your message dated Sun, 18 Jan 2026 12:18:47 +0000
with message-id <[email protected]>
and subject line Bug#1119420: fixed in flobopuyo 0.20-7
has caused the Debian Bug report #1119420,
regarding flobopuyo: 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.)
--
1119420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119420
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: flobopuyo
Version: 0.20-6
User: [email protected]
Usertags: hardening-buildflags
flobopuyo 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 flobopuyo 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
flobopuyo, 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: flobopuyo
Source-Version: 0.20-7
Done: Alexandre Detiste <[email protected]>
We believe that the bug you reported is fixed in the latest version of
flobopuyo, 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.
Alexandre Detiste <[email protected]> (supplier of updated flobopuyo 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: Sun, 18 Jan 2026 12:53:32 +0100
Source: flobopuyo
Architecture: source
Version: 0.20-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team <[email protected]>
Changed-By: Alexandre Detiste <[email protected]>
Closes: 1112277 1119420
Changes:
flobopuyo (0.20-7) unstable; urgency=medium
.
* Team upload.
* Do a verbose build with all flags (Closes: #1112277, #1119420)
* Add debian/salsa-ci.yml
* Rewrite d/rules with newer & shorter syntax
* Bump Standards-Version to 4.7.3, drop Priority: tag
* Remove CDBS leftover from d/rules
* Rename files in debian/ for DebHelper 14 / 15 compatibility
* Rewrite debian/copyright in machine-parsable format
Checksums-Sha1:
ea0d0a4316c3f80fdc781bbcf5df74ffbf50ea74 2041 flobopuyo_0.20-7.dsc
9d2bc91cbce44f6026a81c7790cb3cc4a2ca71aa 8616 flobopuyo_0.20-7.debian.tar.xz
daf76513436068a64e6fd3cf42535c1d3660e51e 12959
flobopuyo_0.20-7_source.buildinfo
Checksums-Sha256:
9646007645222dd8c4ba1f194d63e4d3aec3e2484a0b8c4a92202c6be5eddf3c 2041
flobopuyo_0.20-7.dsc
5ba30dc671031c556d31cfaad8694ef62a679e58607f383157786d8a3c07aba5 8616
flobopuyo_0.20-7.debian.tar.xz
983eb5eb9f8a8e9593018bf4aa329ad0dcf5c04aea0bfef40632f7b4b106a631 12959
flobopuyo_0.20-7_source.buildinfo
Files:
f4c81f0e0796d7da7564901eb3309855 2041 games optional flobopuyo_0.20-7.dsc
eb34d9f8c41133b4018ecb69baaf7791 8616 games optional
flobopuyo_0.20-7.debian.tar.xz
c93edc8b332a0dacff19253a17a68b78 12959 games optional
flobopuyo_0.20-7_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmlsyjIRHHRjaGV0QGRl
Ymlhbi5vcmcACgkQMfMURUShdBobyQ//WfuDZlf0laNlto2JmPUtqVsnq95ft/NI
yH+gPPZspbU8c6x70BW6mwdp2BZnvIVDc96stnb3r5judOI99A6ndH48X+L3R/vR
yko2dwxZ6tSRIjuWhzCtb2a61+Yg3/gOFLIlPuwveLNqU/uoJ8EXCYIb2ADQR9zh
d1hTI4j4CxtibuiDmuLktNNQJQNwUWXqb0/UQRxsN+8yt3wKoTCmlQrLXxbwf+lM
U0h5flcMnyZmZ6NP8P/KrWdPcu+0tc33FGu3Mbx8RP7Kh1EeoZfkMjGT6T5hKlSw
TAPvKhlRd7wpEQ/2N+VGVWEitmT9ym/qGxQ7Fhm+aglUcQ2rxxLrh4pVs+/vQQ4W
4LvazdRfCEdYd8xxcTZHJclQ6BR2/f5a5daB1UhRUN3jEG7C4blmYbQYSoKTtCPs
xaFO20F6+R+gULjEA0y42N/J6vtnovmRYY9Ad2H7K8sQ15WfflcUg08qgzCcKzK+
KeC8EwtRdrVNiraIfyTmbR40yFYjFYAtq7uMJu6r1h+ETh0ZFxrVgaHydfEXHKOS
ehvsytLjBqbNI0NSO1ezMBPWeCx0vnWTabLj/KyhuyXd1sGONRcQcQ9H4voUw8pN
ND1y7aWXDG63XzCosj0fuVBttT8fE8xbsWhTZ//AAMKyZ8Qae5Ay6+Hn082VnkiU
8Ikn+s5jzz4=
=f/lL
-----END PGP SIGNATURE-----
pgp546QA__Atz.pgp
Description: PGP signature
--- End Message ---
