Your message dated Wed, 06 May 2026 11:19:02 +0000
with message-id <[email protected]>
and subject line Bug#1119566: fixed in snibbetracker 1.1.1-6
has caused the Debian Bug report #1119566,
regarding snibbetracker: 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.)


-- 
1119566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119566
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: snibbetracker
Version: 1.1.1-4
User: [email protected]
Usertags: hardening-buildflags

snibbetracker 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 snibbetracker 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
snibbetracker, 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: snibbetracker
Source-Version: 1.1.1-6
Done: Alex Myczko <[email protected]>

We believe that the bug you reported is fixed in the latest version of
snibbetracker, 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 snibbetracker 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, 06 May 2026 10:54:10 +0000
Source: snibbetracker
Architecture: source
Version: 1.1.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <[email protected]>
Changed-By: Alex Myczko <[email protected]>
Closes: 1119566
Changes:
 snibbetracker (1.1.1-6) unstable; urgency=medium
 .
   * Honor default flags. (Closes: #1119566)
Checksums-Sha1:
 f268e3654532f65cdb12127cc243d1eab949de63 2035 snibbetracker_1.1.1-6.dsc
 b0b30d9edffc518c6a88cb4ee54e3febeb900a46 3916 
snibbetracker_1.1.1-6.debian.tar.xz
 85d1199ffa1ed726796bb1315c164045d9c8a4ec 11157 
snibbetracker_1.1.1-6_source.buildinfo
Checksums-Sha256:
 abd80d3eb9cffbf51c0fa398329fb33690308af22cebb35458180fe65aa40391 2035 
snibbetracker_1.1.1-6.dsc
 6bce23154f1fcf3766713c642b7258c7ce753b37ea74dfa4087c4a00b7566559 3916 
snibbetracker_1.1.1-6.debian.tar.xz
 3718d4a2e84e052d50b027f0375754d21c1ba8fef3e90d3ec89592f511ae0a5f 11157 
snibbetracker_1.1.1-6_source.buildinfo
Files:
 b2ecac9b1292e01845ab6c5d04522729 2035 sound optional snibbetracker_1.1.1-6.dsc
 e20ff4c8b30178d4bff179ea9431f47b 3916 sound optional 
snibbetracker_1.1.1-6.debian.tar.xz
 304df6d2c61de04ff66c4df1b56afa51 11157 sound optional 
snibbetracker_1.1.1-6_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJDBAEBCgAtFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmn7Hj0PHHRhckBkZWJp
YW4ub3JnAAoJEBFoUrzfdRXAofYQAJt1U1W0cpHg3T1y8qEqljdU67vwtpyAiT5+
z/MAL2k/CK8ooh71t1pLEAjFM51jN8Y4BNu1NC4QOhmlLW2nGaWafv8ubpP5eM9W
rf3VaHMgY6XQi3O7IsWlCVMXZVDsXLzr/T+m1jtXmzt68+qCKmChNXF0zvIk5MoG
66hK8uzlygbxdR9WvCA9kw2GPF/jsppOjYUQryBvn4S5wFzdd/Ri6qYF+sCoU6y2
hHgf1F/70vkyKNkqZjW/q4o8NnP2PPDgxE8GtEl1nDPVmNfqNiQ5+RbJ2fEePtQC
7RDnIRyYJSKuIVw6Rc0/YeW9UEhWqL681oDgcnTDnRbbwbEk8FFtjI2wa3mQivyn
+JNsPbng7sViZZnMQBx3xm/YEyVDd+RuCAwFxXZNKxUrsqQGi7dBXuJs1M+w+hVn
t7mbSfXzc9jtgdHJA+OXAxygfOeRN2AOmQos0w1zc/A4YG97mWa9YLTdfeyKctWl
7fq3i1s9S237ymdqVwiEU3qUjQuGdTZjrrd5vafb0VuVJJN4asb+lZbq3yhvvkTs
Um+jWhbMPYBJgJzv5ImqbVAoKmNstKhPmJq/vtG4IfpnQkRuWLmuNaEZHfz1VGHC
XENXRsXebrn/KmMDCiU3GjFzTItRl/lZk1LZ0lEopub6ZkdcUn2nZXHYS6igfWJy
fI+MpJaR
=CEB7
-----END PGP SIGNATURE-----

Attachment: pgplH21FOQdjx.pgp
Description: PGP signature


--- End Message ---

Reply via email to