Your message dated Mon, 13 Jul 2026 08:37:09 +0000
with message-id <[email protected]>
and subject line Bug#1119514: fixed in overlay-boot 1.6.3-1
has caused the Debian Bug report #1119514,
regarding overlay-boot: 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.)
--
1119514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119514
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: overlay-boot
Version: 1.2-1
User: [email protected]
Usertags: hardening-buildflags
overlay-boot 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 overlay-boot 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
overlay-boot, 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: overlay-boot
Source-Version: 1.6.3-1
Done: Ralph Ronnquist <[email protected]>
We believe that the bug you reported is fixed in the latest version of
overlay-boot, 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.
Ralph Ronnquist <[email protected]> (supplier of updated overlay-boot 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, 12 Jul 2026 21:05:50 +1000
Source: overlay-boot
Architecture: source
Version: 1.6.3-1
Distribution: unstable
Urgency: medium
Maintainer: Ralph Ronnquist <[email protected]>
Changed-By: Ralph Ronnquist <[email protected]>
Closes: 1119514
Changes:
overlay-boot (1.6.3-1) unstable; urgency=medium
.
* New upstream version.
* Includes Makefile changes to respect build env flags.(closes: #1119514)
Checksums-Sha1:
4caf10be2731a38550b50af08e7ede7e086ce242 1904 overlay-boot_1.6.3-1.dsc
0653ef3549c200b1b883bc26dec998c9b400ec7c 17999 overlay-boot_1.6.3.orig.tar.gz
29154856ef69f8ecc1490da0a1bed09113ef14a5 2664
overlay-boot_1.6.3-1.debian.tar.xz
004755d77edd45f84d69adc6b240c888fbcc4918 6171
overlay-boot_1.6.3-1_amd64.buildinfo
Checksums-Sha256:
9393fb85ef218369b00d8f2e7424715e9ea3b3a9c6cfdc7d8d959c31b2f350e1 1904
overlay-boot_1.6.3-1.dsc
7f5c37df4b5379a892681f6588858b1ea0caa53cb816819c5638bc8c18814a58 17999
overlay-boot_1.6.3.orig.tar.gz
bb64211867c5b4227bdcad99d3ccb6a149f6ff6c886623eca93f70783514b236 2664
overlay-boot_1.6.3-1.debian.tar.xz
0bcc67957202a2badbecc78a48bc4de5ebc7e04f87c6e40255577e350997754a 6171
overlay-boot_1.6.3-1_amd64.buildinfo
Files:
53634a3e1dbda0b8bfb427566714074b 1904 misc optional overlay-boot_1.6.3-1.dsc
261dd204dd7c7cd6dda7f8b4e8611ba9 17999 misc optional
overlay-boot_1.6.3.orig.tar.gz
9d5616aab5177fc601d6fa03a4b2f6b8 2664 misc optional
overlay-boot_1.6.3-1.debian.tar.xz
d1390f3f936a3b9fac1dd593dd0ec30d 6171 misc optional
overlay-boot_1.6.3-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEUGwVpCsK9aCoVCPu0opFvzKH1kkFAmpUldcACgkQ0opFvzKH
1kniaxAAoINQ7nHBzX3OastQHMOtR1hPMPmOhz1HXfCdE+Atbtn3LH6IQwfxlsS8
8u7UF0uqaZdXm9P6qbJ0/+veVGvDxsDVokVw+3sBvd40rAZycs77/tVTVxzHFoai
ncAGqWN6YcwAs9UOFnG1ChpMEXZlD9cTC7hMLwq0RT6pYbrDH4Z9yP8+JFozjhN4
QF4V7fFb6vQAcfwRXo3vT9w3b/plAmbHP6C51TexsU0y1n2u5/CE1FrS8NlZ0V7D
Gb6qNyPI7Hp+Keo/eJT/8zWsPeTktS7QmotrxStN46LKh3EFchi9oSn08si1QtJb
r7l+Tv+SeqvVBu74djI7IHqirnpd4EYLZzaaFw7kltdd1R9hXdokEfTuqCOmwTZH
jSNj0ys6RTyJvMxBq8QD8WzBnxgzIGP7Y9Ob7x6/irRBYguUwcZULoU6JGd14QD9
LHYaHWU6zM+FF1m35an66tCDc+4pQydVqhOs8y/scoVBq2jy2sIjXYvRQJthg8l3
k0R7QHLx9JJv/t8spdardpDlb4hK8AcWB/icCJ9v5BE2A4rz3N/V3abLbVqbGiE4
7uEfOXmoW1twKrOR1uMYgxOcrythIkn7WdgRi+sj1EYAOFHBEBcPCHAJ8sJbUbVs
S0f0U63O1qBEdCVa32qI1iirLxealaHMiALZnnBC0gy/pFv+7Q4=
=xhSz
-----END PGP SIGNATURE-----
pgp5rxSmCZBvG.pgp
Description: PGP signature
--- End Message ---
