Your message dated Tue, 16 Dec 2025 19:34:37 +0000
with message-id <[email protected]>
and subject line Bug#1119359: fixed in bchunk 1.2.2+git20220715+ds-4
has caused the Debian Bug report #1119359,
regarding bchunk: 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.)
--
1119359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119359
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: bchunk
Version: 1.2.2+git20220715+ds-3.1
User: [email protected]
Usertags: hardening-buildflags
bchunk 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 bchunk 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
bchunk, 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: bchunk
Source-Version: 1.2.2+git20220715+ds-4
Done: Alex Myczko <[email protected]>
We believe that the bug you reported is fixed in the latest version of
bchunk, 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 bchunk 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: Tue, 16 Dec 2025 19:16:35 +0000
Source: bchunk
Architecture: source
Version: 1.2.2+git20220715+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Praveen Arimbrathodiyil <[email protected]>
Changed-By: Alex Myczko <[email protected]>
Closes: 1119359
Changes:
bchunk (1.2.2+git20220715+ds-4) unstable; urgency=medium
.
* d/rules: comment CFLAGS. (Closes: #1119359)
* Bump standards version to 4.7.2.
* d/control: drop Rules-Requires-Root.
* Ack NMU.
* d/copyright: bump year.
* d/watch: upgrade to version 5.
Checksums-Sha1:
f8fd7bb2febf8dec1112d02e03c29cedb0bf7ab9 1966 bchunk_1.2.2+git20220715+ds-4.dsc
c95fac44e9a2f0575def2dde6f5690156e06ab86 15152
bchunk_1.2.2+git20220715+ds-4.debian.tar.xz
f1de673ae2cf22cecd4073bf26756129e4421a8f 6396
bchunk_1.2.2+git20220715+ds-4_source.buildinfo
Checksums-Sha256:
b75dccabb73adb87414d0c5364676e8839eab24237663473cc4d82bf1c0ca478 1966
bchunk_1.2.2+git20220715+ds-4.dsc
0a294eb33ede9f2569425b0dd87a8e37656de61a2d305a1f33c400a5ccc5ba67 15152
bchunk_1.2.2+git20220715+ds-4.debian.tar.xz
52e5becac052e7a51795fa4891812af31ea1e3bac9191f5870d46a15d62e5cba 6396
bchunk_1.2.2+git20220715+ds-4_source.buildinfo
Files:
117bcd826f37ba89dd5dddfa96964c2c 1966 otherosfs optional
bchunk_1.2.2+git20220715+ds-4.dsc
5469ed1f7772ad6fe4dcc3be8c0c04b3 15152 otherosfs optional
bchunk_1.2.2+git20220715+ds-4.debian.tar.xz
2016bbbb027dbd03a6d0a4ed0cd69ca1 6396 otherosfs optional
bchunk_1.2.2+git20220715+ds-4_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJDBAEBCgAtFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmlBsTwPHHRhckBkZWJp
YW4ub3JnAAoJEBFoUrzfdRXAIbwP+QG6kkmCEBIwEbd+HHOKqY1l2aYEoKlREuti
uO+jKc5LBAx98y6DThBXh6tzJhrxNLJq9LOX9FZZBxax0FlSQIWBUswuDzj+4VV4
a9lh/vGbbR1wSEaPbLIi27Lckv2CLYPZ/JMNRBKcM91v7b15RDbYiZLATOxtjFwO
vraHkmOptZLJgsoioUFDIrv8YcDY8lvfoOGm0FBgziWmGLJ0hyWWqGWqEaBg7RJN
33slEyC1pt4uN0mwKm6BoOG+Nw4pC+j2NQxGJLaeljgQWkVFx86jmSX0k6rHOuzH
7RVnvqxVnIAxGFovOsPJ4xbDW0JhH1e+fHCPUMwpeEgZ3z4FvZ0UnykOy7NOzPJB
yHRZvutnOCoIWpqKZm/wT02eBio3/e3sNNyTJxleAClOzo2sF2HbrJvQSYENdyyP
nKsFMU8WEPe3VN4vT8t52maMbwmsiKuJfncERVqCRXIf4h+BjsabpWmp+DU9qby7
UHLEk7eZXW+3QBGUlnt54iFw6p+/Czbxxz8wtx069G2GaaDlnj/4O5y70iHK0h71
CkvR/JSCK+6/2sveDZdLQ43BzJlXpoJFqAJUUvimBb9TE5D5ic4K78ld57EZyyRv
3+QHfRdPIEOUw/sL7xJ5ehmwnJLNX+hOOOLGSzzH0qF3jWf/+6ereRQ2UQWd1fyf
vPDIp0rZ
=FiI9
-----END PGP SIGNATURE-----
pgp4gu7yVoa3d.pgp
Description: PGP signature
--- End Message ---
