Your message dated Tue, 11 Nov 2025 22:09:53 +0000
with message-id <[email protected]>
and subject line Bug#1119476: fixed in lunzip 1.15-4
has caused the Debian Bug report #1119476,
regarding lunzip: 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.)
--
1119476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119476
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: lunzip
Version: 1.15-3
User: [email protected]
Usertags: hardening-buildflags
lunzip 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 lunzip 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
lunzip, 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: lunzip
Source-Version: 1.15-4
Done: Daniel Baumann <[email protected]>
We believe that the bug you reported is fixed in the latest version of
lunzip, 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.
Daniel Baumann <[email protected]> (supplier of updated lunzip 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: Tue, 11 Nov 2025 21:13:05 +0100
Source: lunzip
Architecture: source
Version: 1.15-4
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann <[email protected]>
Changed-By: Daniel Baumann <[email protected]>
Closes: 1119476
Changes:
lunzip (1.15-4) sid; urgency=medium
.
* Adding compression option to watch file.
* Removing rules-requires-root, not needed anymore.
* Building with hardening build-flags (Closes: #1119476).
Checksums-Sha1:
7caaf5b93ea346de93cc8ba9b42030359976828c 1186 lunzip_1.15-4.dsc
358dd3423c808573ded1c134ee346a26ead3a75e 6144 lunzip_1.15-4.debian.tar.xz
3585eff5eba722c9f9c47f0008e1cf5d86441d33 5091 lunzip_1.15-4_amd64.buildinfo
Checksums-Sha256:
4d7b766279abe67f75c7f473a536455e930d9f45839ed44600b290532ca76efd 1186
lunzip_1.15-4.dsc
2eeff15eaeecf297e5fa6bc39bdbb87a22eaa3cf7227856eb0183138b551b54d 6144
lunzip_1.15-4.debian.tar.xz
de0d78e220bd145e2664690bd5b3795cfb250d8ba4481e36b191bfeaf6da1d8f 5091
lunzip_1.15-4_amd64.buildinfo
Files:
7189a7696cf6a46681b334668e4dd4a4 1186 utils optional lunzip_1.15-4.dsc
f6686545c8134017983728c9f519fb69 6144 utils optional
lunzip_1.15-4.debian.tar.xz
095a2f39885fd7adc046117c69cc9eee 5091 utils optional
lunzip_1.15-4_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iHUEARYKAB0WIQQmmGg4gLaoSj0ERgL7tPDoCoAiLwUCaROZKQAKCRD7tPDoCoAi
LzrPAP471/e8eiUGMTIVfKjw2f52J3UbpUt0Wpuim5+0OXxrPAD7Bnmb5S9KJOKC
aDlytuAXs2FuUXlppJrbhSEhyFqKSwg=
=1bID
-----END PGP SIGNATURE-----
pgpVDECeMqSJJ.pgp
Description: PGP signature
--- End Message ---
