Your message dated Wed, 25 Mar 2026 07:49:14 +0000
with message-id <[email protected]>
and subject line Bug#1119428: fixed in genromfs 0.5.2-4.1
has caused the Debian Bug report #1119428,
regarding genromfs: 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.)
--
1119428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119428
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: genromfs
Version: 0.5.2-4
User: [email protected]
Usertags: hardening-buildflags
genromfs 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 genromfs 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
genromfs, 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: genromfs
Source-Version: 0.5.2-4.1
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
genromfs, 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.
Andreas Tille <[email protected]> (supplier of updated genromfs 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, 15 Mar 2026 07:50:49 +0100
Source: genromfs
Architecture: source
Version: 0.5.2-4.1
Distribution: unstable
Urgency: medium
Maintainer: Juan Cespedes <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 935741 1086657 1119428
Changes:
genromfs (0.5.2-4.1) unstable; urgency=medium
.
[ Helmut Grohne ]
* Non-maintainer upload.
* Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #935741)
.
[ Andreas Tille ]
* Maintain in Debian team on Salsa
* Add watch file
* d/rules:
- short dh
- hardening
* Use default build flags
Closes: #1119428
* Fix Homepage
Closes: #1086657
* debhelper-compat (= 13)
* cme fix dpkg-control
* d/copyright: Add Upstream-Name and Source
Checksums-Sha1:
ae4b9824453ae34f9901eccb58561d3ab5e49022 1850 genromfs_0.5.2-4.1.dsc
d482fcf46395e0ea7e0d44ba2773398e92fa5a53 3944 genromfs_0.5.2-4.1.debian.tar.xz
733ef082fb0cd10f9c45005355f1103426aef025 5911
genromfs_0.5.2-4.1_amd64.buildinfo
Checksums-Sha256:
5ff3cbebdc803d76e619e331f8afe7cc4872fb1f53acb0a05162e6babb043fdd 1850
genromfs_0.5.2-4.1.dsc
4ff589259d2a68d062ad16df8090c4f6ae28d73481c840cee2ed7cf86fa4ff15 3944
genromfs_0.5.2-4.1.debian.tar.xz
672b8fdee7a70f4801c98dee24da30e38b2078c6bc23b5ef279199134869fbe7 5911
genromfs_0.5.2-4.1_amd64.buildinfo
Files:
9023e5d6b6d656294438f7de1807777f 1850 admin optional genromfs_0.5.2-4.1.dsc
4d9258d1b58960da18292577084c8efe 3944 admin optional
genromfs_0.5.2-4.1.debian.tar.xz
34b7979e439bda94873e33934f94a29d 5911 admin optional
genromfs_0.5.2-4.1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmm2VxQRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFZSw/8Cx/uMw4+7PWLhRKOysQkD/1yMa6zQV9D
5dDxOEtTnkWhmKRyLJI3gP2mxRMyyNtZXypkwmImkSAu1t/YZ3GAxQg4E+m3hG7m
fdKBrxkBhyhlYhZop8f0jleuyl+DHo1Ut/5ctK/KLJpogcLoVPPvtWKex8sLPUsZ
3JPeO6+ISEMMu04h2Txx90I7bmL+4NMeUQMzwZjpR/ifkjPb+ojCZP3H1Cn+9EU8
Jb6xexAanO7dDhpw+rvWcZwcsX9gdYxgF5ey1VqsnyJYZ5BKpwxv0QY2M4KUEx3i
ISyZ+wgIXnOPYs3IppHQ/Xq37Z0JDH/mtHPmjv3jM1bQuFcsDXCBqx4Tk7vbmnm0
EilQaGWUOz8T9xoD7FK6b/UMVgX1fHpVyEnztJJMm5CkKXwFYFBIUAN5HXDlIzoz
usa2h897LOHIO1I3osn3iJOJYGyMiwixbNGbV9IcnjfjXgi7epeoYpgXPT6LpYIt
plOwZ08duwf0xwrmcNOKuzwPkWtxMl7RaqJdME7fAWiss5I2jMdSucM6sqM+pc7r
ZlNoWvifWLxCLXovX/0Co04E6nSTAvI+RTpNhSMztN3e3INU4yVVH7VdAF1UZnWJ
11WRCrm2PROI86gIEYPzzNtXFNwZfiTlWRY1lD7dKs4DADgHJwYS79r0g7rO1eAB
BqNNH5O+I4c=
=5Da0
-----END PGP SIGNATURE-----
pgp58tzUvBOgM.pgp
Description: PGP signature
--- End Message ---
