Your message dated Fri, 14 Nov 2025 06:19:13 +0000
with message-id <[email protected]>
and subject line Bug#1119571: fixed in sredird 2.2.2-1
has caused the Debian Bug report #1119571,
regarding sredird: 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.)
--
1119571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119571
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: sredird
Version: 2.2.2-0.2
User: [email protected]
Usertags: hardening-buildflags
sredird 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 sredird 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
sredird, 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: sredird
Source-Version: 2.2.2-1
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
sredird, 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 sredird 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: Fri, 14 Nov 2025 06:57:18 +0100
Source: sredird
Architecture: source
Version: 2.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1119571
Changes:
sredird (2.2.2-1) unstable; urgency=medium
.
* QA upload.
* Maintain package in Debian team on Salsa
* Add Homepage
* Add watch file
* d/copyright: DEP5
* d/rules:
- Remove "sample" boilerplate comment
- Short dh
* Propagate default build flags
Closes: #1119571
* Standards-Version: 4.7.2 (routine-update)
* debhelper-compat 13 (routine-update)
* debputy lint --auto-fix (routine-update)
* Permit failure of blhc on Salsa
Checksums-Sha1:
b33ea1af1a3f7c27b8d2001cf856f82c66cea800 1852 sredird_2.2.2-1.dsc
8a66b423d26498b0e93f60f97a72ee2da09520f3 3388 sredird_2.2.2-1.debian.tar.xz
47fc03639abd9c94fe904ab0dd9731689cc7dabb 5728 sredird_2.2.2-1_amd64.buildinfo
Checksums-Sha256:
a0484553ee9e5a78365ab83575a51cd5bae490f1d6a05e1e20c973686c3746b4 1852
sredird_2.2.2-1.dsc
3cda2592a41f3117d2557c345e719eabb8435f5382019e3fc71f9a35aea3994a 3388
sredird_2.2.2-1.debian.tar.xz
461da827e9beb79b8328e308b210bc6bd52758b01b56769a784b611847c2dd08 5728
sredird_2.2.2-1_amd64.buildinfo
Files:
2d372986b65d8913271d4537aff07644 1852 comm optional sredird_2.2.2-1.dsc
cca74011d3eeffa3d13f545bccfb659f 3388 comm optional
sredird_2.2.2-1.debian.tar.xz
b390f3cf5cca4c54686b71d53f08992e 5728 comm optional
sredird_2.2.2-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmkWxTMRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHBNw/8Dka8ouPYfspVSItX5SVNz+Q1RcQOfXfD
xPit8fUGqZrDJ94OEzf5evZUW41bRcTDubOovep6YQWJXWuzFU/xr9jWs96DT9ir
C5BS/bjpnU559PvAuBOF9/K42wBj/HmbKyg0PfpuEIVVIY4kslpr/FrQvR8CK0/0
fFN13fYziqiC0rio+JFrus6ve//4IQZlIT/PqtW2xyif/Seq/wYdu+3p2NOrgxxz
pIyRz7E9DlpH9D8SPzdjxNkufsQEXj7rGygH3JAYjSSZpj31oYoqD4dSvfB3uv+t
dxUIEOhJjxLincxdeEQoOYcVnmicjJrzh7y7QgP+nTpcISide2nturSBWeJtqaW9
39xH8pULHccggysnLikvgFwUwYQHBI512ZKYz1pct70Yo5doUTS53pg4VXQAcclW
H7wv2BPxcGOxiCLQVcpTroDgpCb80k/kEYdlanNm8U2Vphz04CrH9Z3+d8FaSPwo
MIRaH/CwNLIUT6okGtx6nTnGUPTwWSPGZKySfKjEcqzZ/QMzO6DidSJAe3pQYXwh
0FitEKXw+9V+TSubAGwFzjoql8osQeAZtExIPQ05TNM8Pe5w6WXeiClYbjwt7whO
HTf83nznxmoeRQsH82TOXyTvVwUPCBN5pwBqvkRDlZQtbRuJXoCPkKcAIWaJcVR2
e6PxUrQZJKM=
=Z4yl
-----END PGP SIGNATURE-----
pgpJOYK79rEFJ.pgp
Description: PGP signature
--- End Message ---
