Your message dated Fri, 02 Jan 2026 18:35:14 +0000
with message-id <[email protected]>
and subject line Bug#1119574: fixed in stardata-common 0.9
has caused the Debian Bug report #1119574,
regarding stardata-common: 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.)
--
1119574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119574
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: stardata-common
Version: 0.8+nmu1
User: [email protected]
Usertags: hardening-buildflags
stardata-common 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 stardata-common 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
stardata-common, 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: stardata-common
Source-Version: 0.9
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
stardata-common, 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 stardata-common 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, 23 Dec 2025 18:39:29 +0100
Source: stardata-common
Architecture: source
Version: 0.9
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers
<[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1119574 1121550
Changes:
stardata-common (0.9) unstable; urgency=medium
.
* Maintain package in Debian Astro Team on Salsa
Closes: #1121550
* d/rules: Short dh
Closes: #1119574
* Remove unused lintian-overrides
* d/copyright: Remove old FSF address
* README: Convert to UTF8
* debhelper-compat 13 (routine-update)
* Remove trailing whitespace in debian/changelog (routine-update)
* Remove trailing whitespace in debian/control (routine-update)
* Remove trailing whitespace in debian/copyright (routine-update)
* Trim trailing whitespace.
* Fix day-of-week for changelog entry 0.4.
* Standards-Version: 4.7.3 (routine-update)
* Remove Priority field to comply with Debian Policy 4.7.3 (routine-
update)
Checksums-Sha1:
2e242517b13f90500aae4071c3ca91065bb65641 1875 stardata-common_0.9.dsc
b9576cd95f5eb9e40e9cdab3fd7c8b29c440ef51 74684 stardata-common_0.9.tar.xz
678d1bcffd1ef6d5157abfc7675211965d4378c0 5985
stardata-common_0.9_amd64.buildinfo
Checksums-Sha256:
67cb0dae1aa595beb3fccc39f9f8e97bacf710195c012da9fd3657e1c7cf9de4 1875
stardata-common_0.9.dsc
a2db461472690274e432fa9596d370598f81c810d088261b4934116c8a6c870b 74684
stardata-common_0.9.tar.xz
e952571cc346543e155e30de01817b1a0854793530378e6a9e425074c3f2f5d5 5985
stardata-common_0.9_amd64.buildinfo
Files:
d7e14b600ad44f400c088a2c90c96e2c 1875 science optional stardata-common_0.9.dsc
63d89a60941fb2d64727c0d26b01ea76 74684 science optional
stardata-common_0.9.tar.xz
c1d512747a39708a21457964988e254b 5985 science optional
stardata-common_0.9_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmlK1DMRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEjWg//dwMxyFjem6pR9WINv1HzVXT5r5cccp0J
RWCD2K21TSicQSCCx1yPCnl1c5p+08Mo6lHZx6ufRg9IqW1heM/d++v6xgA4tix8
2/8Tr9273pT2rc9C02GetJetWl1MCkvRUnhxr/htyBtzsI9Gk4DWTVZNyd4ZKSt5
47VkepKNmY9xQPoc6ff8KuSl6zPA+YAyB1C07k6GzLsPaAu95PMicQKa/y2iSpMb
0CoDwi/DONuZgjus78f84d2UHtIuqpWMDJGEgdF5uho+YFh9Q/tVuo52a60D5krM
0VeLHidCP8uJKazwckgqVBg05o9euFaOax0A7FTSby9ooP/Gf3e7l3ccIFXyLy0G
Q2t6EPlN4gBdr0VwU4klmiJljnWAX3bk77an3rIbxn5IhCyTLjvdjVicZjeJwHlK
y2UUKXRuA6oblAY/1tqBKYEIYYhWCT1THAahExZf/10JdgvcMDxxFSnNJ7tc6C8Q
l40no/CL8CxS7+YOhHJbVz6nVtL6owOM9MmIeNfURXL1p664+T45LRBD+v+m+dFU
4HelZL6kW5UkCt+tqPK3eCpgipGacxlfLy1DLrksUGYPPEpDdjCrNrNSS2mNprME
v17jB/1fycJbt15tTda3Pyd74dN3qmUJtV2EFURX+Ao/OBv3cQqct5QeM9h+URx3
L8TNEQWLMX0=
=Z6SU
-----END PGP SIGNATURE-----
pgpYweSBmrilR.pgp
Description: PGP signature
--- End Message ---
