Your message dated Thu, 29 May 2025 20:58:34 +0000
with message-id <[email protected]>
and subject line Bug#1005282: fixed in systemd 257.6-1
has caused the Debian Bug report #1005282,
regarding systemd: Documentation needed for initramfs copies of *.link files
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.)


-- 
1005282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005282
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 247.3-6
Severity: normal

Dear Maintainer,

Recently I renamed some *.link files on a headless server (changing the names
inside the files to match), but after rebooting the server I was unable to
access it. After much head-scratching I realized that the previous *.link files
had been copied into the initramfs during a kernel package installation some
time in the past, and the new files conflicted with the old ones, so systemd-
networkd could not bring up the network interfaces.

After searching the bug tracker I see that a number of people have been caught
in this 'trap', and the advice given has been to run update-initramfs after
making changes (or adding) *.link files. While that certainly does cure the
problem, I can't find any documentation in the installed system which would
have lead me to know that I needed to do that.

Have I overlooked documentation of this behavior? It doesn't appear in
systemd.link(5), and it doesn't appear in the 'networkd' section of
README.Debian.gz for the systemd package. I can't be certain that this is
Debian-specific behavior (an inquiry about that on the systemd-devel list
hasn't elicited any responses), but it's definitely not 'upstream' behavior.

Please consider documenting this in at least those two places in a very obvious
way. I wish there was a more direct way to notify users that an initramfs
update will be required, but short of having a daemon watch
/etc/systemd/network for changes I can't think of any way to do that.

I'd be happy to provide a patch to add this documentation to those two files if
that would be welcome. Thanks for your time and consideration.


-- Package-specific info:

-- System Information:
Debian Release: 11.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-11-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

Versions of packages systemd depends on:
ii  adduser                          3.118
ii  libacl1                          2.2.53-10
ii  libapparmor1                     2.13.6-10
ii  libaudit1                        1:3.0-2
ii  libblkid1                        2.36.1-8+deb11u1
ii  libc6                            2.31-13+deb11u2
ii  libcap2                          1:2.44-1
ii  libcrypt1                        1:4.4.18-4
ii  libcryptsetup12                  2:2.3.5-1
ii  libgcrypt20                      1.8.7-6
ii  libgnutls30                      3.7.1-5
ii  libgpg-error0                    1.38-2
ii  libip4tc2                        1.8.7-1
ii  libkmod2                         28-1
ii  liblz4-1                         1.9.3-2
ii  liblzma5                         5.2.5-2
ii  libmount1                        2.36.1-8+deb11u1
ii  libpam0g                         1.4.0-9+deb11u1
ii  libseccomp2                      2.5.1-1+deb11u1
ii  libselinux1                      3.1-3
ii  libsystemd0                      247.3-6
ii  libzstd1                         1.4.8+dfsg-2.1
ii  mount                            2.36.1-8+deb11u1
ii  systemd-timesyncd [time-daemon]  247.3-6
ii  util-linux                       2.36.1-8+deb11u1

Versions of packages systemd recommends:
ii  dbus  1.12.20-2

Versions of packages systemd suggests:
ii  policykit-1        0.105-31+deb11u1
ii  systemd-container  247.3-6

Versions of packages systemd is related to:
pn  dracut           <none>
ii  initramfs-tools  0.140
pn  libnss-systemd   <none>
ii  libpam-systemd   247.3-6
ii  udev             247.3-6

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 257.6-1
Done: Luca Boccassi <[email protected]>

We believe that the bug you reported is fixed in the latest version of
systemd, 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.
Luca Boccassi <[email protected]> (supplier of updated systemd 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: Thu, 29 May 2025 17:52:48 +0100
Source: systemd
Architecture: source
Version: 257.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 
<[email protected]>
Changed-By: Luca Boccassi <[email protected]>
Closes: 1005282 1104663 1105743 1106024
Changes:
 systemd (257.6-1) unstable; urgency=medium
 .
   [ Luca Boccassi ]
   * d/copyright: use GPL URL instead of old FSF postal address.
   * d/signing-template/copyright: use GPL URL instead of old FSF postal
     address.
   * d/control: bump Standards-Version to 4.7.2, no changes
   * Add version to systemd-boot-efi-signed virtual package. Otherwise
     dependency on systemd-boot-efi-signed (>= 257.5-2) is not satisfiable
     (Closes: #1104663)
   * systemd-homed: add dependency on polkitd (Closes: #1105743)
   * systemd-boot: fix BOOT.CSV usage (Closes: #1106024)
   * Update upstream source from tag 'upstream/257.6' Update to upstream
     version '257.6' with Debian dir
     907f7fd2ae07adbab0ffd7b9235fc25435f12bab
     (Fixes CVE-2025-4598)
   * Drop patches, merged upstream
 .
   [ Tim Small ]
   * document requirement to sync *.link files with initrd (Closes:
     #1005282)
 .
   [ Kirill Rekhov ]
   * Set upstream metadata fields: Security-Contact
Checksums-Sha1:
 87938213a9da8345691d6c6bac05e26e91afa66f 8614 systemd_257.6-1.dsc
 d9022cbcc23f7a8e08f3779be69139cc4307bfef 16321562 systemd_257.6.orig.tar.gz
 6ae3dbcbc9182966e06e7d196caabce28c35628d 182228 systemd_257.6-1.debian.tar.xz
 8d500b4d27a549ee71f5d860d20e4358745df791 14075 systemd_257.6-1_source.buildinfo
Checksums-Sha256:
 6edd1e36ac1c7759796182701b83f45a9e96c86a708d153ca64a83b82e4383f3 8614 
systemd_257.6-1.dsc
 1ac656c61e595cc6e653883d554caadd2053f323d9065c0daff69f83368b120c 16321562 
systemd_257.6.orig.tar.gz
 e93575db3db98d4f0612798560a1f334ebcaf3033212635dd9d5ee4a11bc1455 182228 
systemd_257.6-1.debian.tar.xz
 4f29e95dc64569d042c06fcfb8cdb0bdd2787061e2112d27c2a6090808826c01 14075 
systemd_257.6-1_source.buildinfo
Files:
 7fbba721bf8da174573a1a8c0e3dc9e4 8614 admin optional systemd_257.6-1.dsc
 458b07e140cd65d25baf7752398c5d13 16321562 admin optional 
systemd_257.6.orig.tar.gz
 794e08b0d1fb23ce41b0c8191d531f50 182228 admin optional 
systemd_257.6-1.debian.tar.xz
 49446e74337626a3d96e8ac006c7be41 14075 admin optional 
systemd_257.6-1_source.buildinfo

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

iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmg4l3gRHGJsdWNhQGRl
Ymlhbi5vcmcACgkQKGv37813JB777xAAigUaGDHOLqMMp7LpfoYOtS/2cCHNIYWU
3b8rrJGH5cNyEcE28qyf3UvQQlYrqhvuyQ1VIY3jjvgb3hfiiX/GMq+vULAlhKxR
9eIIWjNEeJctQIXfkG95bf5ZlqtbzTUCtwZjTxNPiQwArCZJkiSfCwsukLRemTrf
Kvu9J05GCnZfMuGTRjdRkylwLE41vEXJC03qiLDqCbP561rA9RtEs8Ph+NqSCyBN
bxR9zdQsjtyTbwnNod8RiuQXZdDf+y41oBPqW/5FuSvDyUrNQCCl4X1nX+U0mlji
a7N/UlJvawCIq42Rr+YbLqQb9mbs0eV76ETrccFHwrJOmdp24hFtCCF+4N7hnBs+
uIVIo/B7rkeHaBB+IQtepSVIbrwWnykyAMK9RTkmQGBKWK87+mX4vAb48PK/UY1P
fsk16rWxD4Mn535i+aNSwDeJE0SZua+iP4n+vNw7GtZrwIJKLHIr6fyl0zTk5JBM
xv+ejvcgEO6iYM5lfKcA7itdPrqZ14ObJWCq0yQOc9TvlGWv2h/EUbjfJ6sCjrAh
3tU/2gtRJFx3LO3KRq40Dg74i80nRwJEibt/xLtnlNaB1XRwPWeuX2mlbS0ApDaP
wombzmV/soNQhSv0ysytPzwngmCVeTrjs1L5uxLHeUy0/PcxeY8lp7WOhkw9l42Q
M/Y+8TyUrjg=
=4a98
-----END PGP SIGNATURE-----

Attachment: pgpOpvlxPiIYA.pgp
Description: PGP signature


--- End Message ---

Reply via email to