Your message dated Tue, 05 May 2026 20:42:05 +0000
with message-id <[email protected]>
and subject line Bug#1119444: fixed in hp2xx 3.4.4-13
has caused the Debian Bug report #1119444,
regarding hp2xx: 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.)


-- 
1119444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119444
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: hp2xx
Version: 3.4.4-12+b2
User: [email protected]
Usertags: hardening-buildflags

hp2xx 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 hp2xx 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
hp2xx, 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: hp2xx
Source-Version: 3.4.4-13
Done: Christian T. Steigies <[email protected]>

We believe that the bug you reported is fixed in the latest version of
hp2xx, 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.
Christian T. Steigies <[email protected]> (supplier of updated hp2xx 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, 05 May 2026 21:58:49 +0200
Source: hp2xx
Architecture: source
Version: 3.4.4-13
Distribution: unstable
Urgency: medium
Maintainer: Christian T. Steigies <[email protected]>
Changed-By: Christian T. Steigies <[email protected]>
Closes: 1119444
Changes:
 hp2xx (3.4.4-13) unstable; urgency=medium
 .
   * Use default build flags (Closes: #1119444).
   * Update standards-version to 4.7.4, drop redundant Priority field.
   * Fix "format not a string literal and no format arguments" error.
   * Use autopkgtest.
Checksums-Sha1:
 8f48023abe067cee962c33edda46ff085dac251f 1911 hp2xx_3.4.4-13.dsc
 9784c58309136d3f7cb81a65bff1cb695707847b 7556 hp2xx_3.4.4-13.debian.tar.xz
 a083d0a2061009a43d14467af308cda303c34911 7907 hp2xx_3.4.4-13_amd64.buildinfo
Checksums-Sha256:
 68aff4ad6b50ccdbf0bdd33d2f204c6271a926767b69633889b0acbfb80ba497 1911 
hp2xx_3.4.4-13.dsc
 0fc8255a60ec59e1b5db6d45724baab764430bc645f474b7aa90b05f7e62e23f 7556 
hp2xx_3.4.4-13.debian.tar.xz
 2456d6c98eb5cf41efcc0ea86a21e5579894bd678a3ff7fcfd9b8e041e5fcf76 7907 
hp2xx_3.4.4-13_amd64.buildinfo
Files:
 544c818d913113f2e77f6a1cdb79b574 1911 graphics optional hp2xx_3.4.4-13.dsc
 53786aa2c7412cf9da6d3b3b90ae18d7 7556 graphics optional 
hp2xx_3.4.4-13.debian.tar.xz
 6531f2d5835cd9cfde116b27012ec1f6 7907 graphics optional 
hp2xx_3.4.4-13_amd64.buildinfo

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

iQJDBAEBCgAtFiEEMuHemUY/GC4Wej4EcA1WeHGyg0IFAmn6TOQPHGN0c0BkZWJp
YW4ub3JnAAoJEHANVnhxsoNC0EEP/i4zeX06UYPYpCqPWOTcdU43HlriAjPBlG24
ffG7+AUhQ0M9MA96AXM7CdLI/oL4TzJeoQgV4JW3TVu9ioUhKwPSWwEQRQPjznTU
7nEjWVi4WuS8hek46Wq4FvaEp3x2xIqCbTQGaZ2wF+WoBvCw2vzDSvJZ5stZIcpd
5UGJbCMZiZ1usGvc+/LYJygRH2T/qpAjzE117ol/vzz2HdQNsDNuOK2CGdwQ/DOb
38fvuu0L8kGR1MSsQiahxYD63/qrAYmaI6Du6ojsd6Z84soUJl7Pu/TBXWIdttc9
dWAxjhE2ICkXWK/qWOOSvt5PNyQLQEGpW9y0toauybXpkdmnFIsYkl/fgNy8h1b2
hI/YbQuffzM4cMCfiiZt/DFgXupLWwgONXQlCf/71mgVTSH3gow56q0FsSv2wWJh
QQ02c8p79RyC3/bxQF4vYM2TentEZ+QGLnzArKW8gTwqbaTUSyfLc0Sr3g72cRfx
DvVcQW3mltlCOEslR+3+QYep3iMyUeiTbZ4XBcUJgYWiyoQCy1FQg2XNdMsYyyEy
kSZy3pX1Bhy8eP/yzYItLSpkEU3BCLxbZfIjDjZ7gHNfCBAn00k1QvNiBwV8gSI/
oUiZrEBePoXD6oX6MoTciiyiKSzDCSGHpJnPMNnmJXxuKAn4frsf+bBt5dAlQYjn
pTZ/gnpo
=C8c6
-----END PGP SIGNATURE-----

Attachment: pgp9YAefHvqR1.pgp
Description: PGP signature


--- End Message ---

Reply via email to