Your message dated Sun, 02 Oct 2022 21:22:24 +0000
with message-id <e1of6po-00hi0v...@fasolo.debian.org>
and subject line Bug#1020396: fixed in systemd 251.5-1
has caused the Debian Bug report #1020396,
regarding systemd-boot: kernel installation/initrd update hooks double the
initrd like #970213 since #826045
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 ow...@bugs.debian.org
immediately.)
--
1020396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd-boot
Version: 251.4-3
Severity: normal
Tags: patch
Dear Maintainer,
In the default installation, both a bare initrd and a versioned one are
installed:
/boot/efi/HASH/5.16.0-1-amd64/initrd.img-5.16.0-1-amd64
/boot/efi/HASH/5.16.0-1-amd64/linux
/boot/efi/HASH/5.16.0-1-amd64/initrd
In #970213, I worked around this by only installing the generated
as the standard "initrd" fallback if none was passed;
I've been using a simple
#!/bin/sh
bootctl is-installed > /dev/null || exit 0
exec kernel-install add "$1" "/boot/vmlinuz-$1" "/boot/initrd.img-$1"
/etc/kernel/postinst.d/kernel-install (and analogous remove),
so this works for that case perfectly.
In #826045, upstream hooks were added:
debian/extra/kernel/post{inst,rm}.d/systemd-boot
(74127387dacf23f037f3a55a808951fae93024c6)
and
debian/extra/initramfs/post-update.d/systemd-boot
(9a6d87f1c6f7fbde8ff8e7beab30973944221244)
to integrate with bootctl out-of-box. This is great!
However, /etc/kernel/postinst.d/systemd-boot runs:
kernel-install add "$1" "$2"
and /etc/initramfs/post-update.d/systemd-boot runs:
kernel-install add "$1" "/boot/vmlinuz-$1" "$2"
And the former installs:
/boot/efi/HASH/5.16.0-1-amd64/linux
/boot/efi/HASH/5.16.0-1-amd64/initrd
but the latter installs:
/boot/efi/HASH/5.16.0-1-amd64/initrd.img-5.16.0-1-amd64
/boot/efi/HASH/5.16.0-1-amd64/linux
hence the situation at the top I wanted to avoid in #970213;
ESPs tend to be really small!
I've opened MR 169 on Salsa:
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/169
and am attaching a patch for this that makes it so
/etc/kernel/postinst.d/systemd-boot calls
kernel-install add "$1" "$2" "/boot/initrd.img-$1"
if the latter exists, and the previous
kernel-install add "$1" "$2"
otherwise, which always installs the versioned initrd,
as well as one that will order this bootloader hook
with the other bootloader hooks at the end (cf. message).
Installation logs that demonstrate this follow.
Implicit image:
root@zoot2:~# kernel-install -v add $(uname -r) /boot/vmlinuz-5.16.0-1-amd64
Reading /usr/lib/kernel/install.conf…
BOOT_ROOT=/tmp/br set via environment or install.conf
machine-id d42f27f4670847aeae24b01bd283a4e0 acquired from /etc/machine-id
Entry-token candidates: d42f27f4670847aeae24b01bd283a4e0 debian Default
/tmp/br/d42f27f4670847aeae24b01bd283a4e0 exists, using BOOT_ROOT=/tmp/br,
ENTRY_TOKEN=d42f27f4670847aeae24b01bd283a4e0
/tmp/br/d42f27f4670847aeae24b01bd283a4e0 exists, using layout=bls
Using ENTRY_DIR_ABS=/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64
Plugin files:
/usr/lib/kernel/install.d/50-depmod.install
/usr/lib/kernel/install.d/85-initrd.install
/usr/lib/kernel/install.d/90-loaderentry.install
+mkdir -v -p /tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64
mkdir: created directory
'/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64'
+/usr/lib/kernel/install.d/50-depmod.install add 5.16.0-1-amd64
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64
/boot/vmlinuz-5.16.0-1-amd64
+depmod -a 5.16.0-1-amd64
+/usr/lib/kernel/install.d/85-initrd.install add 5.16.0-1-amd64
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64
/boot/vmlinuz-5.16.0-1-amd64
Installing '/boot/initrd.img-5.16.0-1-amd64' as
'/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64/initrd'
+/usr/lib/kernel/install.d/90-loaderentry.install add 5.16.0-1-amd64
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64
/boot/vmlinuz-5.16.0-1-amd64
Creating
/tmp/br/loader/entries/d42f27f4670847aeae24b01bd283a4e0-5.16.0-1-amd64.conf
root@zoot2:~# find /tmp/br/
/tmp/br/
/tmp/br/loader
/tmp/br/loader/entries
/tmp/br/loader/entries/d42f27f4670847aeae24b01bd283a4e0-5.16.0-1-amd64.conf
/tmp/br/d42f27f4670847aeae24b01bd283a4e0
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64/linux
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64/initrd
Explicit image:
root@zoot2:~# kernel-install -v add $(uname -r) /boot/vmlinuz-5.16.0-1-amd64
/boot/initrd.img-5.16.0-1-amd64
Reading /usr/lib/kernel/install.conf…
BOOT_ROOT=/tmp/br set via environment or install.conf
machine-id d42f27f4670847aeae24b01bd283a4e0 acquired from /etc/machine-id
Entry-token candidates: d42f27f4670847aeae24b01bd283a4e0 debian Default
/tmp/br/d42f27f4670847aeae24b01bd283a4e0 exists, using BOOT_ROOT=/tmp/br,
ENTRY_TOKEN=d42f27f4670847aeae24b01bd283a4e0
/tmp/br/d42f27f4670847aeae24b01bd283a4e0 exists, using layout=bls
Using ENTRY_DIR_ABS=/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64
Plugin files:
/usr/lib/kernel/install.d/50-depmod.install
/usr/lib/kernel/install.d/85-initrd.install
/usr/lib/kernel/install.d/90-loaderentry.install
+mkdir -v -p /tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64
mkdir: created directory
'/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64'
+/usr/lib/kernel/install.d/50-depmod.install add 5.16.0-1-amd64
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64
/boot/vmlinuz-5.16.0-1-amd64 /boot/initrd.img-5.16.4
+depmod -a 5.16.0-1-amd64
+/usr/lib/kernel/install.d/85-initrd.install add 5.16.0-1-amd64
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64
/boot/vmlinuz-5.16.0-1-amd64 /boot/initrd.img-5.16.4
+/usr/lib/kernel/install.d/90-loaderentry.install add 5.16.0-1-amd64
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64
/boot/vmlinuz-5.16.0-1-amd64 /boot/initrd.img-4
Installing
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64/initrd.img-5.16.0-1-amd64
Creating
/tmp/br/loader/entries/d42f27f4670847aeae24b01bd283a4e0-5.16.0-1-amd64.conf
root@zoot2:~# find /tmp/br/
/tmp/br/
/tmp/br/d42f27f4670847aeae24b01bd283a4e0
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64/initrd.img-5.16.0-1-amd64
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64/linux
/tmp/br/loader
/tmp/br/loader/entries
/tmp/br/loader/entries/d42f27f4670847aeae24b01bd283a4e0-5.16.0-1-amd64.conf
One then the other:
root@zoot2:~# kernel-install -v add $(uname -r) /boot/vmlinuz-5.16.0-1-amd64
/boot/initrd.img-5.16.0-1-amd64
Reading /usr/lib/kernel/install.conf…
BOOT_ROOT=/tmp/br set via environment or install.conf
machine-id d42f27f4670847aeae24b01bd283a4e0 acquired from /etc/machine-id
Entry-token candidates: d42f27f4670847aeae24b01bd283a4e0 debian Default
/tmp/br/d42f27f4670847aeae24b01bd283a4e0 exists, using BOOT_ROOT=/tmp/br,
ENTRY_TOKEN=d42f27f4670847aeae24b01bd283a4e0
/tmp/br/d42f27f4670847aeae24b01bd283a4e0 exists, using layout=bls
Using ENTRY_DIR_ABS=/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64
Plugin files:
/usr/lib/kernel/install.d/50-depmod.install
/usr/lib/kernel/install.d/85-initrd.install
/usr/lib/kernel/install.d/90-loaderentry.install
+mkdir -v -p /tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64
+/usr/lib/kernel/install.d/50-depmod.install add 5.16.0-1-amd64
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64
/boot/vmlinuz-5.16.0-1-amd64 /boot/initrd.img-5.16.4
+depmod -a 5.16.0-1-amd64
+/usr/lib/kernel/install.d/85-initrd.install add 5.16.0-1-amd64
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64
/boot/vmlinuz-5.16.0-1-amd64 /boot/initrd.img-5.16.4
+/usr/lib/kernel/install.d/90-loaderentry.install add 5.16.0-1-amd64
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64
/boot/vmlinuz-5.16.0-1-amd64 /boot/initrd.img-4
Installing
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64/initrd.img-5.16.0-1-amd64
Creating
/tmp/br/loader/entries/d42f27f4670847aeae24b01bd283a4e0-5.16.0-1-amd64.conf
root@zoot2:~# find /tmp/br/
/tmp/br/
/tmp/br/loader
/tmp/br/loader/entries
/tmp/br/loader/entries/d42f27f4670847aeae24b01bd283a4e0-5.16.0-1-amd64.conf
/tmp/br/d42f27f4670847aeae24b01bd283a4e0
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64/initrd.img-5.16.0-1-amd64
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64/linux
/tmp/br/d42f27f4670847aeae24b01bd283a4e0/5.16.0-1-amd64/initrd
-- System Information:
Debian Release: 11.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-17-amd64 (SMP w/24 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND,
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd-boot depends on:
ii libc6 2.31-13+deb11u4
pn libsystemd-shared <none>
pn systemd-boot-efi <none>
Versions of packages systemd-boot recommends:
ii efibootmgr 17-1
systemd-boot suggests no packages.
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 251.5-1
Done: Michael Biebl <bi...@debian.org>
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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Biebl <bi...@debian.org> (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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sun, 02 Oct 2022 21:23:49 +0200
Source: systemd
Architecture: source
Version: 251.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers
<pkg-systemd-maintain...@lists.alioth.debian.org>
Changed-By: Michael Biebl <bi...@debian.org>
Closes: 844528 877414 1014581 1020396
Changes:
systemd (251.5-1) unstable; urgency=medium
.
[ Michael Biebl ]
* New upstream version 251.5
* Install NEWS.Debian file into all binary packages.
While it increases the disk footprint a little, it ensures that NEWS
entries are reliably shown by apt-listchanges.
* Handle removal of /var/log/README.
Remove /var/log/README symlink when the systemd package is purged.
This symlink is created via tmpfiles and documents that /var/log no
longer contains the traditional syslog text files. (Closes: #877414)
* Rebase patches
.
[ наб ]
* debian/extra/kernel/postinst.d/systemd-boot: prefix with zz-
Since we explicitly (though this is hidden by indirection through
85-initrd.install) depend on /boot/initrd.img-$1 existing or not existing,
hard-order ourselves at the end. The zz- prefix matches grub.
* debian/extra/kernel-install.d/85-initrd.install: install default initrd
with versioned basename.
This fixes #1020396 in a superior way by using
$KERNEL_INSTALL_STAGING_AREA, available since systemd v251.
By just copying the file we both simplify our code, but defer to
90-loaderentry to correctly permission it, and simply never generate an
unversioned initrd in the first place! (Closes: #1020396)
* debian/extra/kernel-install.d/85-initrd.install: explicitly ignore unknown
verbs
* debian/extra/kernel/postrm.d/systemd-boot: prefix with zz-
Doesn't actually matter, but the kernel handbook says we must and we
already renamed postinst. (Closes: #1014581)
.
[ Luca Boccassi ]
* Enable firstboot, disabled by default on Debian.
Currently the first-boot conditions are not met by any Debian
image (/etc/machine-id with content uninitialized, so we can
just enable the build and ship it in the main package.
This lets image builders (eg: cloud images) tinker with it.
https://www.freedesktop.org/software/systemd/man/machine-id.html#First%20Boot%20Semantics
(Closes: #844528)
Checksums-Sha1:
b7075589bf53acde45bb7dbf388fad71c94d5f51 6244 systemd_251.5-1.dsc
88d8bef4e914d56f7117166317a42aac919061ad 11444428 systemd_251.5.orig.tar.gz
e158f7fad33574f6e0245def62e15c1483e787c8 172076 systemd_251.5-1.debian.tar.xz
126fd86e2957235c9b783e043c4de85fb266074c 10458 systemd_251.5-1_source.buildinfo
Checksums-Sha256:
ade68055bac2af2286bd87abf28241fb2009f82703a052c8bbc23b86cc49d279 6244
systemd_251.5-1.dsc
5ac1e9dad7032561e2040ca7e4bacf4be045c4899bab4d72613d041a0401bf5f 11444428
systemd_251.5.orig.tar.gz
13cd419f4177a4a2fdbdf3798363e3130a47b74f0246357e06f89942075d5347 172076
systemd_251.5-1.debian.tar.xz
28150cb9c2332c9a54dc5ad8628230347f801a13e0f97301c92d92073226f6bd 10458
systemd_251.5-1_source.buildinfo
Files:
6677763dd8f2ce28ef2e49f3682b1355 6244 admin optional systemd_251.5-1.dsc
d26d9f41600e4d5f7142eccf079b8044 11444428 admin optional
systemd_251.5.orig.tar.gz
10e9869bf91b58fefb94f87283c32d49 172076 admin optional
systemd_251.5-1.debian.tar.xz
4f86009b0ab407dc2fe9a4ece331f8d3 10458 admin optional
systemd_251.5-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAmM57V4ACgkQauHfDWCP
ItxjuA/9GVPHkJR7BkVYGyl+8B1LJk100nIXBGAraHNdb7c1Fmo4xTRM9ubU+yAd
DdqBMJrUPiBzjJdnmHb6U13dYe7udhU2di6gFtYmlVjUeQj2xlvXB7psrt3fDXMu
n3PI7yWSb7YkBt+N+rOb0DzddnfoRczpVSzuH+zCNgGvTWwF+HI3FqtczKNKNPKq
ScC1Ie0Y+OSt+BBIAfkwZbVJyjchxD6pqbMe3GZU2sKjBIbbElGhtaLYuZKrSOa5
ewh+8hw9uLmgdNrzbGfQ1Uo5GeNQtGa9V8ntjVNqwWPcCC66rEz/uHDINO6etgNj
E31CsQy19BJbHdlfzucFVdDnytu26yJTFIEKzZ40V9Us3UyTqDgjGSvzTSr1y01r
kfhTIp1n/TrInO6J4y2Am+/rVmXaHSjjzAa1lJxr53Gv1Zp81cmPjkOfostr6zW8
scXHwsrBrXBIKsYKMM7f/f9rFIIL8Fr0tg41dJLueY8rbg8o+N0ySCs9Fg+jqW1M
5YkH3WNw54yqyDFC85mPv0+zq8fBCf6grGDuHXIIEpAXN772UYkiQ/dyaM8MODoe
8CiovyrvaqTgdX19MboHPREXzpXDZ6ap7LkkH78xJqmOPP1PVeeTzeTqkoNsTTcw
KIjvRHFvgKTCpw5OoWqBaOyD9U6oB5e67vdMb0MJiXh8KbR4tdM=
=YmZd
-----END PGP SIGNATURE-----
--- End Message ---
