Your message dated Sat, 20 Jun 2026 13:49:08 +0000
with message-id <[email protected]>
and subject line Bug#1119426: fixed in gcpegg 5.1-19
has caused the Debian Bug report #1119426,
regarding gcpegg: 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.)


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

gcpegg 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 gcpegg 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
gcpegg, 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: gcpegg
Source-Version: 5.1-19
Done: Andreas Tille <[email protected]>

We believe that the bug you reported is fixed in the latest version of
gcpegg, 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.
Andreas Tille <[email protected]> (supplier of updated gcpegg 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, 20 Jun 2026 15:21:25 +0200
Source: gcpegg
Architecture: source
Version: 5.1-19
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1119426
Changes:
 gcpegg (5.1-19) unstable; urgency=medium
 .
   * QA upload.
   * Maintain package in Debian team on Salsa
   * Add debian/salsa-ci.yml
   * Secure URI to Global Consciousness Project
   * d/copyright: DEP5
   * d/rules: Short dh
   * Respect Debian build flags
     Closes: #1119426
   * d/rules: Hardening
Checksums-Sha1:
 c9bd6f647600f4e35c2494016caea47ec5f9886b 1823 gcpegg_5.1-19.dsc
 03fd8946e2171fbffc490b558632f7a075b4c940 14196 gcpegg_5.1-19.debian.tar.xz
 e78ac0f061981def21d4e3c63d11e3374aecd765 5997 gcpegg_5.1-19_amd64.buildinfo
Checksums-Sha256:
 04da6c7abe7bb031ff6e37c978e17484e3ee1e561e9aa75fc7d2a73657282ce7 1823 
gcpegg_5.1-19.dsc
 5c0cc02bbe7a3a2db8085935382f7feabc915c39023365fb82ac2b7f09f138a1 14196 
gcpegg_5.1-19.debian.tar.xz
 b307b6d82007ee4714d297c680133fd70cf8789670f32b4e0e0074a141c072f4 5997 
gcpegg_5.1-19_amd64.buildinfo
Files:
 f0165f058b22c16f36de822ac371452a 1823 misc optional gcpegg_5.1-19.dsc
 9f6f68a79715c2e63b09d92f14de67b9 14196 misc optional 
gcpegg_5.1-19.debian.tar.xz
 2a71483cc8620e35b9002437ee66a25b 5997 misc optional 
gcpegg_5.1-19_amd64.buildinfo

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

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmo2lp8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHvyQ//YGrJ9fGrN8ycRRtCyrbWUjHmJg+veiY7
/mh26he/2QdhTGEapNsRbqTiwyJbLZGXDpgixB2Pxs3FNszAUKJrBwpgz3mpWOQ7
J7LCKeyaHP0LkanOF9CtBxnqlJ0xQdF3H+pEETTIrvsklJOp3XNTkZlP2ZSBsd8/
jINjW5sjFVVkKYBepw9qfl7JBmtkCFROBreYAO+FuqdNn50XhUDlLzZiXTYNABVF
0uTPxkXLhAxRPxUNNZpxuW7gxrYwE4OVfVsYupeUVhg9GKCPtDRR+eDk1V0ddxUU
eE3Ji8YLBUdQJNU0MwJBtY606DZ4wAQdt7dYvUcRVODXgs131AYislei6zduF+xc
I2QyX9Oxfmo5UeG8Bxm4EqcwNn4j5EkLH3zExmNJNitT6TTEN69UiPyvOhETdnVB
3rM+AnJ/rgdLl4ifDdEG2fWODIy6/T4H2eNz+p4p8f4RDCr5BJtC4VqQ57LAEgcK
Cu5pX/VGqoNgPMvS/VZ2W0+GTEF7CCr5uGOpTSCwxR5A24nPbSp3p4Su0d6b0hTM
S4BNv84M2y7HzJ6orGSrcS+u9NKKKu2apxAUhPs1gwO8sOeJNzrlU7v3M1GtBXA+
OZGZX+BV5KLrlPPlC8SnT4Apd1iboafEh+k5VIpbaeCRw5L8uGxnZUCUVTHlCBV3
v5Nmeo6VJD8=
=myt4
-----END PGP SIGNATURE-----

Attachment: pgpIol20I_DZE.pgp
Description: PGP signature


--- End Message ---

Reply via email to