Your message dated Wed, 07 Jan 2026 11:47:38 +0000
with message-id <[email protected]>
and subject line Bug#1124878: fixed in lzlib 1.15-5
has caused the Debian Bug report #1124878,
regarding lzlib: 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.)
--
1124878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1124878
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: lzlib
Version: 1.15-4
User: [email protected]
Usertags: hardening-buildflags
lzlib 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 lzlib 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
lzlib, 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://hal.science/hal-05334704/
--- End Message ---
--- Begin Message ---
Source: lzlib
Source-Version: 1.15-5
Done: Daniel Baumann <[email protected]>
We believe that the bug you reported is fixed in the latest version of
lzlib, 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 lzlib 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: Wed, 07 Jan 2026 11:55:57 +0100
Source: lzlib
Architecture: source
Version: 1.15-5
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann <[email protected]>
Changed-By: Daniel Baumann <[email protected]>
Closes: 1124878
Changes:
lzlib (1.15-5) sid; urgency=medium
.
* Updating to standards version 4.7.3.
* Building with hardening build-flags (Closes: #1124878).
* Updating years in copyright for 2026.
Checksums-Sha1:
52736422904750c636d04046dd04a12d7b7bfdb8 1285 lzlib_1.15-5.dsc
e5e2370a84418fdaae54c68200b3570f103a322b 7592 lzlib_1.15-5.debian.tar.xz
cec8720789733063d698d0924e630f7d6efaf9dc 6460 lzlib_1.15-5_amd64.buildinfo
Checksums-Sha256:
320edc4e3be9eed5095e5e2d0b99e2217e85d1fd39c02cdabf0a09455b6b5a17 1285
lzlib_1.15-5.dsc
b2eb2717fcaa72ff69a0270921120c74348410aa20953c0b22746f8bbd008050 7592
lzlib_1.15-5.debian.tar.xz
8013d064add3ff9112cbc41d594879fce076d6e155e4386f52caadec9855cda7 6460
lzlib_1.15-5_amd64.buildinfo
Files:
f5891477432532c49e05d6bf67a9bed8 1285 libs optional lzlib_1.15-5.dsc
0ce1fd5e83ed2d4db95c425a94cad6b3 7592 libs optional lzlib_1.15-5.debian.tar.xz
2f55db57f30bbe257763741a558ed33b 6460 libs optional
lzlib_1.15-5_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iHUEARYKAB0WIQQmmGg4gLaoSj0ERgL7tPDoCoAiLwUCaV48GQAKCRD7tPDoCoAi
L92WAP4jjsaBg529u2qL2G935Z7MxSx9T7Du21UwIocDEyMi+gEAsLeonzj1eqEe
P3vAr12pXQuDFmtPk6+/8kHR/704sgM=
=B7+/
-----END PGP SIGNATURE-----
pgprdnEJwNkyF.pgp
Description: PGP signature
--- End Message ---
