Your message dated Mon, 24 Nov 2025 08:49:12 +0000
with message-id <[email protected]>
and subject line Bug#1121138: fixed in mmc-utils 1.0-2
has caused the Debian Bug report #1121138,
regarding mmc-utils: consider undefining either Debian's _FORTIFY_SOURCE or 
upstreams
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.)


-- 
1121138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1121138
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: mmc-utils
Severity: wishlist
X-Debbugs-Cc: [email protected]

Hello there, dear maintainer!

Ubuntu currently carries multiple weird patches, all mostly due to the use of 
_FORTIFY_SOURCE=3 there.
The upstream package already sets _FORTIFY_SOURCE=2, which doesn't conflict 
with Debian, so everything is fine here.
Still, it's not very idiomatic in the sense that if one day Debian changes its 
value, there will be a conflict, because specifying multiple time 
_FORTIFY_SOURCE with different values is not allowed.

The version currently in Debian (1.0-1) doesn't build with _FORTIFY_SOURCE=3, 
so keeping upstream's value kinda make sense, but also prevents catching more 
issues with stronger checks.
I've no idea how upstream would consider removing that definition to let 
distros free to choose, and/or bumping the value to 3 with some code changes to 
build with that, so I'll leave that to you.

In the meantime, would you consider the following debdiff to make the package 
more friendly to downstream distros that set a different value for 
_FORTIFY_SOURCE?
```
diff -Nru mmc-utils-1.0/debian/rules mmc-utils-1.0/debian/rules
--- mmc-utils-1.0/debian/rules  2025-08-16 23:44:39.000000000 +0200
+++ mmc-utils-1.0/debian/rules  2025-11-21 17:34:23.000000000 +0100
@@ -1,6 +1,7 @@
 #!/usr/bin/make -f
export DEB_BUILD_MAINT_OPTIONS = hardening=+all
+DEB_CPPFLAGS_MAINT_APPEND=-U_FORTIFY_SOURCE
 DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/buildflags.mk
 include /usr/share/dpkg/pkg-info.mk
```

Thanks
Skia



-- System Information:
Debian Release: forky/sid
  APT prefers resolute
  APT policy: (500, 'resolute'), (500, 'questing-updates'), (500, 'questing'), 
(200, 'noble-updates'), (200, 'noble-backports'), (200, 'noble'), (100, 
'resolute-proposed'), (100, 'questing-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.17.0-6-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message ---
Source: mmc-utils
Source-Version: 1.0-2
Done: Nobuhiro Iwamatsu <[email protected]>

We believe that the bug you reported is fixed in the latest version of
mmc-utils, 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.
Nobuhiro Iwamatsu <[email protected]> (supplier of updated mmc-utils 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: SHA256

Format: 1.8
Date: Mon, 24 Nov 2025 17:16:36 +0900
Source: mmc-utils
Architecture: source
Version: 1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu <[email protected]>
Changed-By: Nobuhiro Iwamatsu <[email protected]>
Closes: 1121138 1121260
Changes:
 mmc-utils (1.0-2) unstable; urgency=medium
 .
   * d/rules
     - Add Makefile-Drop-D_FORTIFY_SOURCE-2.patch. (Closes: #1121138)
     - Fix FTCBFS: Use dh_auto_build. (Closes: #1121260)
Checksums-Sha1:
 56abb259ccc55c37f968e66e3a267338a3981c7c 1854 mmc-utils_1.0-2.dsc
 df50ac1d0f0dde9fcfeaf7d74ec1c1a0e67e0011 5248 mmc-utils_1.0-2.debian.tar.xz
 ebc543fd50893114c19f91a20ee877986fba9df6 5897 mmc-utils_1.0-2_amd64.buildinfo
Checksums-Sha256:
 757d47e3057628f64b5828b6ed2db08abce918c4a10c32a8efb8702805efdd97 1854 
mmc-utils_1.0-2.dsc
 9afd4711f221c46e6da66a4d2e26b0f09ab83aef9b66065f835742864a4796b2 5248 
mmc-utils_1.0-2.debian.tar.xz
 78b00fcd3cc794839da5d3b1d070b4217a7cce7ed38adce7ff2823e02ee40494 5897 
mmc-utils_1.0-2_amd64.buildinfo
Files:
 bcd8aeda55ea4e1a36d35525f8b51923 1854 utils optional mmc-utils_1.0-2.dsc
 7728a0c0fa12acfa615c3897d8e3766b 5248 utils optional 
mmc-utils_1.0-2.debian.tar.xz
 b12748f14f3b86de4e5440bffe5e39e3 5897 utils optional 
mmc-utils_1.0-2_amd64.buildinfo

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

iQIzBAEBCAAdFiEEXmKe5SMhlzV7hM9DMiR/u0CtH6YFAmkkFjoACgkQMiR/u0Ct
H6afuA//bsM+sD6c5lBeBk4x6Bpmvn8OCJjCkAhjsp/zALM2GOs8BaynNx42ALm9
ZVwdppAHWCOPWCoIFOaPyy2IlHMwo5kvvxUmnmdxgBdXiUgj8cxsTRnoAeClQR+c
MWxMFRlvR5Yx9/pgjL42XI9areX4Twdc5PPnxUdJmjkTVzvCUs4/iYv9wH2yNvZb
3CWjb7GczE8F26j2CFkadJ8PY4LLNWe+chibevRUeM6SnzTtFbpi6SzURvimnbwV
CwsrGXNy7/njpwfQbRubqJeV2/loJpgnw2UCfui5zY5x+30FgE8GpefaZWCCPWc9
pJn9pgbE3J59jAYyexJkweA1KEblgsyUhq9RFoj9w5jY3Z9Ys/r/kR4d3Cv6NDXB
Ba7EXYguhdXuS8dAGnv0qaCMQPIRLpx1m14rXnstRSFoo1lbzmf974NJF4fXDEAs
H4XsGO8rtLXhumVjEruqujdySal4uv9lMcu2ABx1vN4WS6yPFpyqB+45MjRKXQ60
5hB6Lid6unOngNxeMICj5j/xa1Sb1oA2WMadhHlSPBT9tqqSj/chowC3seSSnJh8
n1VaD5uimPa0JXfFB524HuAqtpDhlwdB7xWSuptNG2Wk4XeO24VzE30b0T9jIx8L
5RqrzhZMXj3cx4x0aq4Ohx7N+MdXmBvgjTkUzFduCFcq4dxzrlw=
=xEAH
-----END PGP SIGNATURE-----

Attachment: pgpw3c_5mkKy8.pgp
Description: PGP signature


--- End Message ---

Reply via email to