Your message dated Wed, 29 Oct 2025 21:11:33 +0000
with message-id <[email protected]>
and subject line Bug#1119361: fixed in birthday 1.6.2-8
has caused the Debian Bug report #1119361,
regarding birthday: 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.)
--
1119361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119361
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: birthday
Version: 1.6.2-7
User: [email protected]
Usertags: hardening-buildflags
birthday 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 birthday 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
birthday, 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: birthday
Source-Version: 1.6.2-8
Done: наб <[email protected]>
We believe that the bug you reported is fixed in the latest version of
birthday, 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.
наб <[email protected]> (supplier of updated birthday 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, 29 Oct 2025 19:07:45 +0100
Source: birthday
Architecture: source
Version: 1.6.2-8
Distribution: unstable
Urgency: medium
Maintainer: Package Salvaging Team <[email protected]>
Changed-By: наб <[email protected]>
Closes: 1119361
Changes:
birthday (1.6.2-8) unstable; urgency=medium
.
* Team upload.
* d/rules: fold override_dh_installman into execute_before_dh_installman
* d/local/vcf2birthday.1: unbreak, fix, rewrite in mdoc
* d/local/vcf2birthday: chmod +x
* d/local/vcf2birthday: reject invalid usage instead of ignoring it
* d/p/0010: Don't override CFLAGS (Closes: #1119361)
* d/README: fix vcf2birthday call
Checksums-Sha1:
7b4413a1311d8b7a4dcec5a79694accdd8fa0764 1967 birthday_1.6.2-8.dsc
07ceb463e62cf52d7177b3c9617f8f48d879afdb 108610 birthday_1.6.2.orig.tar.gz
46a5fd334faa6a1ffeada27c5be2d3f6e5d92ef5 14896 birthday_1.6.2-8.debian.tar.xz
fc624912c1e97b94330ebfdbfb7cc593be7e37ec 6930 birthday_1.6.2-8_source.buildinfo
Checksums-Sha256:
63cc60d60fe63dcf008b9fa8554eba09f349b084e4aa07c1f2b9517881421bb1 1967
birthday_1.6.2-8.dsc
3010d82595b1a4927ed1107175b042c1aac42118a7b2cf01f1fa03359441097f 108610
birthday_1.6.2.orig.tar.gz
9c49b0c538b9cf047933869b6b5d7b659e0f32c6736afbf87102fbfeff66c00a 14896
birthday_1.6.2-8.debian.tar.xz
e1c5cf2bab10a311568e9eadafe91d29d1cbc8683465d3d35861bfc3633762f2 6930
birthday_1.6.2-8_source.buildinfo
Files:
e88411caa8ec03ac8ec560177b116280 1967 misc optional birthday_1.6.2-8.dsc
3c7b111a69fbcd01d462a28456384ae4 108610 misc optional
birthday_1.6.2.orig.tar.gz
a45ad7cdd509ffff04138c4004fad645 14896 misc optional
birthday_1.6.2-8.debian.tar.xz
9f8466497324623c99dbe330166abe01 6930 misc optional
birthday_1.6.2-8_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJWBAEBCgBAFiEEfWlHToQCjFzAxEFjvP0LAY0mWPEFAmkCWNwiHG5hYmlqYWN6
bGV3ZWxpQG5hYmlqYWN6bGV3ZWxpLnh5egAKCRC8/QsBjSZY8fKED/9AXxoVfUnh
jaxZetSZBjmkDUCLp77LTt9BjGXuf4+N/c6NLOGz4Z0nNhecLc+hO3Rk9FFneGkh
fPSd7qakudJJmwJmJbuI18LqzG/oZaVWL+Ow56SWxtErt5YOc9t6vph5TyQ/ZcUL
EU1OuFj3w0TNZ7Z1kvLursCUCGSUVG7xgZ2mL3MEkYAOV1nLjM3JzMe4Y+jQOZUA
aM/wpXJxDYQGhBjCYZfFLlsAHxzbrwj9bXVmmNSvlZ+yAxopB9XNtRFGFHzIceyN
x+nKPwqPtxIcjyvgbvzWqol7469h0Hr4qOMd/mJg6b+T8KrFofLC9X6jue7F2R5M
HhIjfLXdpw9upeHcEq47+DiXuCJciSUHkI26jup5ck/jSFVIfGJEqDC5OkguC71R
HsmQVItNtDck0OO/25wy3W8RkR6dQzWgc2nqnv85+/JVy9FjDE/ohFYlEzIehoY4
FT+rFEJKN41Qz5k/ZtV9ooTZgbdhHs236A6tjIcE5yf0xI8c6zQxskFq6SiM5APm
T00+t7TkMciJE9bpeQ+aEHdrxBR2DavFafl+DV6ecxziUl8Z5N6EhFSKJsfMd4su
f5St7AmAavcUJL3cYBW4EOUymQIw5Yz4mD4MmLgmIOwSUbUUwghGRSStC28zFh6V
hPiTU5ohhF0UDUyPLHEMomtNEbC0HjcpQA==
=x6Qy
-----END PGP SIGNATURE-----
pgpucNl6fnlQj.pgp
Description: PGP signature
--- End Message ---