Your message dated Sun, 10 May 2026 19:35:21 +0000
with message-id <[email protected]>
and subject line Bug#1124853: fixed in erlang 1:29.0~rc3+dfsg-4
has caused the Debian Bug report #1124853,
regarding erlang: 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.)
--
1124853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1124853
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: erlang
Version: 1:27.3.4.6+dfsg-1
User: [email protected]
Usertags: hardening-buildflags
erlang 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 erlang 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
erlang, 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: erlang
Source-Version: 1:29.0~rc3+dfsg-4
Done: Sergei Golovan <[email protected]>
We believe that the bug you reported is fixed in the latest version of
erlang, 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.
Sergei Golovan <[email protected]> (supplier of updated erlang 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, 10 May 2026 19:57:06 +0300
Source: erlang
Architecture: source
Version: 1:29.0~rc3+dfsg-4
Distribution: experimental
Urgency: medium
Maintainer: Debian Erlang Packagers <[email protected]>
Changed-By: Sergei Golovan <[email protected]>
Closes: 1124853
Changes:
erlang (1:29.0~rc3+dfsg-4) experimental; urgency=medium
.
* Sort modules in erlang-depends for reproducibility.
* Add --enable-deterministic-build to the configure options for
reproducibility.
* Use -n option for gzip when compressing manpages for reproducibility.
* Respect SOURCE_DATE_EPOCH when generating footers of HTML docs for
reproducibility.
* Use the default build flags (closes: #1124853).
Checksums-Sha1:
5ee3165fced84df1b16971218746289bdb7e1b43 4933 erlang_29.0~rc3+dfsg-4.dsc
231e516149408180400d264bc14c5b5f1bd85760 58164
erlang_29.0~rc3+dfsg-4.debian.tar.xz
eb0fa58f936a5fbce828c5961002259c3675fdd7 30182
erlang_29.0~rc3+dfsg-4_amd64.buildinfo
Checksums-Sha256:
91f548df238296757f7b7eea52cd1381b93eecb8a2a5b6ed48a7bbc43c67e651 4933
erlang_29.0~rc3+dfsg-4.dsc
929a7fb527e72438e32baa1b08c8b9e60992df25018ec962136e0dde89c294a6 58164
erlang_29.0~rc3+dfsg-4.debian.tar.xz
38b376d726f1500fbe0e38ea51e422df6b63f1a9cca59f43c4ff22436b926fc5 30182
erlang_29.0~rc3+dfsg-4_amd64.buildinfo
Files:
cccd7e829a54b146feebe5ae7ac0584f 4933 interpreters optional
erlang_29.0~rc3+dfsg-4.dsc
911d9db0976275a65b153545ab81658e 58164 interpreters optional
erlang_29.0~rc3+dfsg-4.debian.tar.xz
141af92141e50f3ce4840b312b46972e 30182 interpreters optional
erlang_29.0~rc3+dfsg-4_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE/SYPsyDB+ShSnvc4Tyrk60tj54cFAmoAyUEACgkQTyrk60tj
54c73Q//Tylhcgg5T7RzYyP/Bk13/FUeRIuHs/Na/oUulPdf0KdGpessnxXFxzUz
Hg47R0J0pBbGfb3b6SwdWpTmXTCT6NtozmWtLv0UJ/Vll4+J8N07BY3XhrbcHvEB
OaCtHzLnvHSkBglMr4k3qYZ6qC9x9UbWwvbs1FM9WBDQE/cph5l+gF7ekr0Wxk8U
4vQF2qOq+9N2xAxEKvIdy2QS7v6rj+zwKpvVgcckIptx6N+sS8RMllew8WvQvTFG
lbU7rXaCTsSm6KymHP4GcuDF3qaA5aFS83hpFNUQDmaOOqfwbH9XO4w+BOsCjGKN
bdTWieR0Bxg1N/zCq0eENPKRSx5GNCXSRGJ/Sjx85AH3JF+r2ReS7AyHbiWLtt8o
PPJFFIrAxv2yGbSxl9lhChzkkV2R4KanFC0CNHyVixpAlX4fzBmoNV7IOmIa6qXi
LaDGNXELpgWVbp3+IVmYueQh56Fnkmz/XMK+N/+Q2cmF8u85hXgJCu8yr2X4hbBn
FSiU3mYjGZ2r3h5H0EP7R8ZE/tubHCF7EfWAQgEEAYZ2EuEuCjnXkDDaFGjT9Jfm
QFlxPL4pAFDm5RWhgjs511+ZX02tuugCdPoufQUIIPbtl4jEaGyx76QfuEPEpMv4
0AuXS5HjvE7QIBB5Ax5glGWX/6Pyc5+/UMmEMI7nPt/TxP2QMUU=
=dyfr
-----END PGP SIGNATURE-----
pgpeNJdTTHI58.pgp
Description: PGP signature
--- End Message ---
