Your message dated Sun, 11 Oct 2026 03:19:06 +0000
with message-id <[email protected]>
and subject line Bug#1124858: fixed in gio-qt 0.0.16-2
has caused the Debian Bug report #1124858,
regarding gio-qt: 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.)
--
1124858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1124858
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: gio-qt
Version: 0.0.16-1
User: [email protected]
Usertags: hardening-buildflags
gio-qt 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 gio-qt 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
gio-qt, 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://hal.science/hal-05334704/
--- End Message ---
--- Begin Message ---
Source: gio-qt
Source-Version: 0.0.16-2
Done: Boyuan Yang <[email protected]>
We believe that the bug you reported is fixed in the latest version of
gio-qt, 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.
Boyuan Yang <[email protected]> (supplier of updated gio-qt 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, 10 Oct 2026 22:42:52 -0400
Source: gio-qt
Architecture: source
Version: 0.0.16-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Deepin Packaging Team
<[email protected]>
Changed-By: Boyuan Yang <[email protected]>
Closes: 1124858
Changes:
gio-qt (0.0.16-2) unstable; urgency=medium
.
* debian/patches: Preserve externally supplied C++ compiler flags.
(Closes: #1124858)
* debian/control: Bump Standards-Version to 4.7.4; drop redundant
Priority and Rules-Requires-Root fields.
Checksums-Sha1:
759328b79babf004c2c9b84f5207ab78b1ea72e2 2185 gio-qt_0.0.16-2.dsc
a464db454f61439b14fde503a77ba67605441423 41116 gio-qt_0.0.16.orig.tar.xz
36ce6850ce5a4f994b7dce809b81fa603287545c 8536 gio-qt_0.0.16-2.debian.tar.xz
860ef65ef4a6522fa9c49e5d1389e50d4bab71e1 14718 gio-qt_0.0.16-2_amd64.buildinfo
Checksums-Sha256:
52d8c76ec1f6f1d3455c6c94997c99456fce627d8fe27d128749cbe9833b6c9b 2185
gio-qt_0.0.16-2.dsc
0d841559d167aa6393afd2523445b4555b6874ccde346430e26df964e58e4e67 41116
gio-qt_0.0.16.orig.tar.xz
362e2523825bf5e1e8c4176385735d93014bb4b4db89b5cff9e6c8d1566962f7 8536
gio-qt_0.0.16-2.debian.tar.xz
de20d9eb9b7b5fb2c1f3fe2766ac0b792562ec055d9166e7346dae2cd82a4335 14718
gio-qt_0.0.16-2_amd64.buildinfo
Files:
52070710ecab16b42dfb2f496fc73ca1 2185 libs optional gio-qt_0.0.16-2.dsc
7bb1826f9c67dc9cf5eab2fedc272990 41116 libs optional gio-qt_0.0.16.orig.tar.xz
12e733c30a0ad30784b060dbdc2cf4b1 8536 libs optional
gio-qt_0.0.16-2.debian.tar.xz
fdae7a453c2b8841706a64d50ed569ee 14718 libs optional
gio-qt_0.0.16-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmrK+20ACgkQwpPntGGC
Ws4cXRAAoXwRVqYrv5WCwIBBGxvJ6X6rlh06PsRWKqqur928BLnDvjYSnJOBcGUK
ClZYQ3m2dz/DojgaT2i/ZVPC7PEUtRs7NPqGhaE61/t6ZFhBVKKL8EE2TbAeMs/L
busDkG92EuIfTNsyJTq1mdf5LKm4v4SqxMjKu2hb9T7dvnQefW20yeBcc0+LJCxi
6s2tgV2ZW4TrVeZh0a4APv5MPRL9/VYIJAxSbXWao4jdsXpuxlkd3bJM5sX0mOQD
xcSazR2IuXdC+TsiWFaSCuO1aKAP1Q9a9SaITSr/6+7bwdrGXp4ATcpiUNvSrGmh
bZPsWlQlm3XuTgpD9C3I/8PA+QmPUfl2iETofM97QiG2ghsWj+OstZJvwyMhAqo5
aDNTuxcBkasQ90oWWyldwwydmUYkfKHVxtYJ0nGVdJ6ENMuznWil60m3UdEskaEe
20cBOUhy7BNFRHHicD7Ue2wLFPGAAUnLzg6AyMRz2q3O+GU2ZC45eRs0L0HoD3wJ
PTB5UnxjoQsMQ6/0hVRwV8o4q07jXD0I0bAsirDL0FislsBSyGVSOg72phqKhCxk
dqaekbuWf736/oEOcHkznzVyory+i3lF7M7Suf3XX+/5zTECHM7oT7Peo6t3+Ajq
XYmxISGWTCiDGKy8XDg/ls2RFCmVp4mf3t90437J1sr3FR+YWF8=
=y4hp
-----END PGP SIGNATURE-----
pgptvzz6BFf0E.pgp
Description: PGP signature
--- End Message ---
