Your message dated Wed, 13 Aug 2025 11:52:57 +0000
with message-id <[email protected]>
and subject line Bug#1100100: fixed in postfix 3.10.3-3
has caused the Debian Bug report #1100100,
regarding postfix: configure-instance's cp call fails on overlayfs over nfs4
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.)
--
1100100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100100
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: postfix
Version: 3.10.1-1
Severity: important
Hi,
I'm facing an issue on a ephemeral machine booted into a read-only nfs4
root with an overlayfs to make / writable. postfix doesn't start, since
the copy command in configure-instance:91 fails. It copies the data, but
overlayfs has an long-standing issue with nfs4_acls [1], which cp -p will
try to copy but fail. The files are thus copied over and on the next
start of postfix, the service will start without any issues (complaing
again about the same problem for copying the libraries in Line 109, which
is ignored though by the trailing || : in this line.
Is there a specific reason to copy these files with -p? From what I can
tell, they're all word-readable and owned by root:root, so maybe
preserving timestamps (if that is intended) would be enough? From the
commit introducing -p [2], It seems like this was done to have more
readable code.
That would solve this issue for this specific scenario without
interfering with other installations as far as I can tell.
I acknowledge that this should ideally be fixed in overlayfs for a
general solution, but in hope of getting a faster solution, I wanted to
ask if you'd consider changing the cp options.
Best,
Cornelius Hoffmann
[1]
https://lore.kernel.org/linux-fsdevel/cajfpeguwutrwrgmnmimnp-fxzwqmccqmb24iwpu0w_j0_ro...@mail.gmail.com/
[2]
https://salsa.debian.org/postfix-team/postfix-dev/-/commit/ca82392182402ab7de571346d27345e6644952d2
-- System Information:
Debian Release: trixie/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing'), (99, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.17-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages postfix depends on:
ii adduser 3.137
ii debconf [debconf-2.0] 1.5.89
ii init-system-helpers 1.68
ii libc6 2.40-7
ii libdb5.3t64 5.3.28+dfsg2-9
ii libicu72 72.1-6
ii libnsl2 1.3.0-3+b3
ii libsasl2-2 2.1.28+dfsg1-9
ii libssl3t64 3.4.1-1
ii libtlsrpt0 0.5.0rc1-2
ii netbase 6.4
Versions of packages postfix recommends:
ii ca-certificates 20241223
ii python3 3.13.2-1
pn ssl-cert <none>
Versions of packages postfix suggests:
ii emacs-nox [mail-reader] 1:30.1+1-4
pn libsasl2-modules | dovecot-common <none>
pn postfix-cdb <none>
pn postfix-doc <none>
pn postfix-ldap <none>
pn postfix-lmdb <none>
pn postfix-mongodb <none>
pn postfix-mta-sts-resolver <none>
pn postfix-mysql <none>
pn postfix-pcre <none>
pn postfix-pgsql <none>
pn postfix-sqlite <none>
pn procmail <none>
pn sasl2-bin | dovecot-common <none>
ii systemd-resolved [resolvconf] 257.3-1
pn ufw <none>
-- debconf information:
postfix/main_mailer_type: No configuration
postfix/bad_recipient_delimiter:
postfix/rfc1035_violation: false
postfix/protocols:
postfix/mynetworks: 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
postfix/mailbox_limit: 0
postfix/recipient_delim: +
postfix/relayhost:
postfix/destinations:
postfix/root_address:
postfix/procmail:
postfix/not_configured:
postfix/mailname: /etc/mailname
--- End Message ---
--- Begin Message ---
Source: postfix
Source-Version: 3.10.3-3
Done: Michael Tokarev <[email protected]>
We believe that the bug you reported is fixed in the latest version of
postfix, 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.
Michael Tokarev <[email protected]> (supplier of updated postfix 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, 13 Aug 2025 14:29:46 +0300
Source: postfix
Architecture: source
Version: 3.10.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Postfix Team <[email protected]>
Changed-By: Michael Tokarev <[email protected]>
Closes: 1100100 1110704
Changes:
postfix (3.10.3-3) unstable; urgency=medium
.
* configure-instance.in: fix typo
* configure-instance.in: limit maxdepth=1 in /etc/ssl/certs dirs
* configure-instance.in: use home-grown file copy procedure to sync chroot
There are a few issues with using cp(1) to update files in chroot, -
a file should be copied even if the source date is *less* than the
target date (eg, if a package has been downgraded), which is not done
by `cp -u` (#1110704), a file should be copied atomically (copy+rename,
not truncate+copy), and care should be taken with extra attributes
(#1100100). Use a simple perl-based script (using just perl-base)
to update files instead, which fixes all this stuff.
(Closes: #1100100, #1110704)
Checksums-Sha1:
c26c38db4886933d218bfa39954df57bf285004b 3161 postfix_3.10.3-3.dsc
ac27fa96c007f06a66a67bb49ea4ecb406197359 198636 postfix_3.10.3-3.debian.tar.xz
a782b3d05177bc7b3724575acee66d1ebc8b7146 5840 postfix_3.10.3-3_source.buildinfo
Checksums-Sha256:
cea9db9021a69ff7d87dd843cd08ecf284f1d9aaa32bfc31eabd435d3d98617c 3161
postfix_3.10.3-3.dsc
63c38dab6f483cefa1508160a8ade03c0b4c1a1a12d85451d5ac9acafdc15f77 198636
postfix_3.10.3-3.debian.tar.xz
e3be649bd2f2e5cc952a4275fc44a6744a27ec76a8dced34ced1aa15ff632056 5840
postfix_3.10.3-3_source.buildinfo
Files:
4eb2698a79c568e0d5fbc9542ebe9b0a 3161 mail optional postfix_3.10.3-3.dsc
5b6f572de81eacc9a8fd988e9e9ecec1 198636 mail optional
postfix_3.10.3-3.debian.tar.xz
bf8e473e61bebd6e8f36234ea67d936e 5840 mail optional
postfix_3.10.3-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEZKoqtTHVaQM2a/75gqpKJDselHgFAmicd04ACgkQgqpKJDse
lHhnOhAAuZI/EoyDWI7btJ0SWLXyN6WL4PJJ8OSFsZgeNYHUzIhuTP24VERtOlIi
wk4Z2WV/GMyDwK3NYUoYCdSmMWkJGu5m3mVwmia7mnlT4Ii3So6x2Udd+jw/HCCs
J9xXRfMsXe85m/TVnAXEoyM9pR+jjuEzievs3F1HQ3Zv9r1hrUyQDbZHbAnf69QB
XbqWpTQefxX274qIVvxZcJ5gSM85M5HL5aPpbZDYOgFRP7tScefpmCADDYD94139
KRz4TdFp3JfnyiiMUwj8GZnEoXGxrJsx8gnaX1YNoahdD00rnRN0u3wcy3D3PcFj
Cm1tqkTHDaszw3VvZalsnlFnyAfbNE4nnC5yIuhGtgpB11B3I1XMnSCN//0TKVLf
caefbSpvbAYIiv2tL4aiBYB6KE2GwNNj0gtt5TpeWf3FL9As+MV1LUKLYlqvWTiy
S785Cnu2KsuvMfobY+p9ySbvXHtV0+LwDSGh+1Kn5j+4KNbHA4V9ywOzwh5Us0Wu
hSVXR9r/ftWR2lmUBVHeorb1W5fP80enl0WGmEPgAsiNtECeIb3ll19pkTjHdIvl
LYDPZdR5qbWLEj2SAO5kh+H6PoyW+B7WzqLhI3FZrHmjiWimdRDr606Ylngf3PnX
H2Vi0SAb4mzeSNTO8PK3zWuYPx44TratjR1n2u2N3s2BEfZcaDM=
=aM1p
-----END PGP SIGNATURE-----
pgp2V9FcTHoYs.pgp
Description: PGP signature
--- End Message ---
