Your message dated Sat, 01 Nov 2025 18:58:11 +0000
with message-id <[email protected]>
and subject line Bug#1119513: fixed in osmo-tetra 0.0~git20230902.c0956b9-3
has caused the Debian Bug report #1119513,
regarding osmo-tetra: 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.)
--
1119513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119513
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: osmo-tetra
Version: 0.0~git20230902.c0956b9-2
User: [email protected]
Usertags: hardening-buildflags
osmo-tetra 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 osmo-tetra 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
osmo-tetra, 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: osmo-tetra
Source-Version: 0.0~git20230902.c0956b9-3
Done: Thorsten Alteholz <[email protected]>
We believe that the bug you reported is fixed in the latest version of
osmo-tetra, 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.
Thorsten Alteholz <[email protected]> (supplier of updated osmo-tetra 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, 31 Oct 2025 09:56:01 +0100
Source: osmo-tetra
Architecture: source
Version: 0.0~git20230902.c0956b9-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Mobcom Maintainers
<[email protected]>
Changed-By: Thorsten Alteholz <[email protected]>
Closes: 1119513
Changes:
osmo-tetra (0.0~git20230902.c0956b9-3) unstable; urgency=medium
.
* take care of CFLAGS (Closes: #1119513)
(amend hardening-no-fortify-functions.patch)
Checksums-Sha1:
18dbff6f6899cedca9a4ca5b6162c2764127db86 2383
osmo-tetra_0.0~git20230902.c0956b9-3.dsc
4a87152482139b494e33517bed3036e2551e836e 76972
osmo-tetra_0.0~git20230902.c0956b9.orig.tar.xz
bfb38b11850b0d877e9c029b29151a857ec9fe98 4580
osmo-tetra_0.0~git20230902.c0956b9-3.debian.tar.xz
7a69ea5ebef7b26d9035056b3c78d7201be6276e 17649
osmo-tetra_0.0~git20230902.c0956b9-3_amd64.buildinfo
Checksums-Sha256:
644cb9e8d661fcf4f7ab15676c2a2e1b8212a1ddcf19e8e959ec010567c49eb4 2383
osmo-tetra_0.0~git20230902.c0956b9-3.dsc
4339ea6448c14e9a47e48a21acef97238689e1a5da8700bada5430e272e16346 76972
osmo-tetra_0.0~git20230902.c0956b9.orig.tar.xz
3b7a2f410e293f00cff5690ed613315d4d7e4d1374b62bfbaf91e227d77d1455 4580
osmo-tetra_0.0~git20230902.c0956b9-3.debian.tar.xz
ace1040639cb6c0cc453f35f7ccae0fa1237a74a23981c6e24c7f5772edb9011 17649
osmo-tetra_0.0~git20230902.c0956b9-3_amd64.buildinfo
Files:
4867bcfc1471cb6012f3b081203054ff 2383 comm optional
osmo-tetra_0.0~git20230902.c0956b9-3.dsc
fd48c6b2d6dbf23f770ea80790764924 76972 comm optional
osmo-tetra_0.0~git20230902.c0956b9.orig.tar.xz
efb98c1f2315f604e636f9f16f20e8dc 4580 comm optional
osmo-tetra_0.0~git20230902.c0956b9-3.debian.tar.xz
63b716fd8d230726dd58bfda298f3973 17649 comm optional
osmo-tetra_0.0~git20230902.c0956b9-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmkGUX5fFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh
bHRlaG9sei5kZQAKCRCW/KwNOHtYR5LVD/4i32//fStYqfH9ZR1t+hWoNbwpshcn
eQBRgzdeQHCLPftBzhSYcDL5SE7Z7O7vpZI535M2bxKJpk1be0f+Vuye7kijeAND
tNRA88+8wr6jPGJyM7Stzd8OpEzybfrRXCggCcwHnUNMLyILESlxn/60WnddU0t7
/3Ac/DEXi6T9IZuI/CHO+bR6FFciiptKg1HGFbhL0I6IH6V7AylJQZWIHK3CRzRf
MD5XPvuGr++ihRbMdH7KpLC1i5PZAcgDhsjLjZJKMqYufPbJS7JzT+o6E11H2+xQ
0Sd6e8yi9jKv9Mj9ZPr/Gu5yNbBTNiZng9fcpjFYav7OFCvejbWoOO2qy253aWoe
Gx6kabX/DBMrEUFc9vaUPZ5zkGAVbEbLGNAV9YoBtIaKFLqukT7IlVQmX7CAHN3E
SXuULipqtuPdk/rGitW8KB5j7v6oca365AnEAR++dJ6oPRkBkUowgQyMHBRgbiBB
dhe3lnyscsjocjr0uT0/vSG8mvg02rC0uCYE3hilyj+EgE0DPG3BQuwQjHAgCdVu
YQ1ypM0FtFjHUJr7oLNKbI617LEs6/WvvwNW4rzm0l3sxm3FktH15JuQhXTsZ9W1
mWQ36EFOfKfQu0YDzY1WXI/q6ogZZC3tlj/OAOq2H/CwvTdP8s2UvDpa0EHx1zEW
bjcpRAb01r46UA==
=Z5yt
-----END PGP SIGNATURE-----
pgpHIVmxLV4Ww.pgp
Description: PGP signature
--- End Message ---
