Your message dated Sat, 16 May 2026 16:49:16 +0000
with message-id <[email protected]>
and subject line Bug#1119639: fixed in zytrax 0+git20250217+ds-3
has caused the Debian Bug report #1119639,
regarding zytrax: 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.)
--
1119639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119639
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: zytrax
Version: 0+git20250217+ds-2+b1
User: [email protected]
Usertags: hardening-buildflags
zytrax 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 zytrax 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
zytrax, 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: zytrax
Source-Version: 0+git20250217+ds-3
Done: Alex Myczko <[email protected]>
We believe that the bug you reported is fixed in the latest version of
zytrax, 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.
Alex Myczko <[email protected]> (supplier of updated zytrax 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: Sat, 16 May 2026 16:08:42 +0000
Source: zytrax
Architecture: source
Version: 0+git20250217+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <[email protected]>
Changed-By: Alex Myczko <[email protected]>
Closes: 1119639
Changes:
zytrax (0+git20250217+ds-3) unstable; urgency=medium
.
* Build using default flags. (Closes: #1119639)
Checksums-Sha1:
4a3ba07951b9bde1a19423ae5fc153f6189c702b 2087 zytrax_0+git20250217+ds-3.dsc
fdf24cddfc1d936920294267be14a544d544e843 4392
zytrax_0+git20250217+ds-3.debian.tar.xz
55097b9442deff851277b36be25d3e678a4fadc3 15918
zytrax_0+git20250217+ds-3_source.buildinfo
Checksums-Sha256:
2136cb9cc9248daed4eaea51eef83358024783804329c07366befeb598368200 2087
zytrax_0+git20250217+ds-3.dsc
691122b0906d880d16fcdbf7322cd2161fa52ba981b9c3f1a44b6322351ec547 4392
zytrax_0+git20250217+ds-3.debian.tar.xz
a7773acddf1f2b408855c9bef39bd6601985e6358b975df2cbfd27305d5b749e 15918
zytrax_0+git20250217+ds-3_source.buildinfo
Files:
b1171144ff7f90bbc3c8e61e29f5bead 2087 sound optional
zytrax_0+git20250217+ds-3.dsc
c49323798009a148bf7148da591064e8 4392 sound optional
zytrax_0+git20250217+ds-3.debian.tar.xz
d9fbcb4a5efc9aa9c4bc991a9512a1c1 15918 sound optional
zytrax_0+git20250217+ds-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJDBAEBCgAtFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmoImxQPHHRhckBkZWJp
YW4ub3JnAAoJEBFoUrzfdRXA1zcP/RjRLpPxJIcrPLUqGUQR5Bp5SvaOuHrnTHjl
Ho9/nc1eHnseCvIzgjCbm009rfbp1WlhKEvi9fHlVQ5vOSyNLv46wtFxbobbo11F
xLt7+hhMkPyj8QNiB08+rGqYZ80w0PXDm1eimDh/rttR1C6QU2F0Bdqfr0zlzFzH
qiriUlKB9W2YMecD+E3qKTlT3bf6EfImdPDK0HoiiC1QmZGZjgHvF/LFqBpnmddx
F8hp0Q+53qoYdK25B5yFdnrdVDs/9lg2sDVrJPoW7kvEMerqP6yE+If/iCHPZBHu
aIjb7vE/Xf6lRwhbtaWaL1UTKt8IssU+L9rrUZVtO1ta4QjrQX+X2Neo6EOpb+ZX
KaP9ItqHOXwvtzd9rkwkzb2yqqeAe/EWm0QSr2Cb6Ah8nJEwBYz8NP5N3DnSQJ1/
JGg9Yv111T06qWfu6Eg+fX4PT/W69EYsUvYd0wa/nwKscoG04M3AI69XK8j3aJDV
f/ZNq7LMVJ/mxIGSDj3nbd9qnyiFq+rNGt47yRRi5lS6+yBUUAo3wvuXF4ONDU7g
E2Qk7OqRGhmaMWSymmPluwrK7knJIUi/0eVvbv7HghzU0JztTciskoZaAiXGQ11l
EDhpWZHmdy9JYuYL7B+qcPFRpb2DgBExf6NeFPa4SwHxYts8sBrFp28KZKsIIvop
CY2cPhUc
=X5+9
-----END PGP SIGNATURE-----
pgproYLRXI1M7.pgp
Description: PGP signature
--- End Message ---
