Hi everyone,
a few minutes ago I accidently issued "apt update && apt upgrade && apt dist-upgrade" at my PVE host. Thought I was within some other host I don't care too much about instead and ran into a conflict by APT with the file mentioned in the subject. As I didn't care too much, I just kept it as is, but afterwards recognized that I was on the host, where I do care about how to properly solve those conflicts. The following is the output of APT I still have:
I can't remember to have ever executed proxmox-boot-tool in a way to trigger those changes. So I believe at some point some update or ... provided by the maintainer made that tool being called and changed that file. But then, the maintainer should have been aware of such a conflict most likely and would have addressed that already?!
I had a look at the file APT kept and if I understand the code correct, the new and old file have the same safety checks and should gracefully not do anything, because "bootctl is-installed" would end with an error, making the script abort. But there's a reason most likely why theyx even changed it to hard-coded "exit 0" in the old version already.
So, how does that file needs to look like right now? Can I just put the new file from the maintainer into place?
Thanks!
a few minutes ago I accidently issued "apt update && apt upgrade && apt dist-upgrade" at my PVE host. Thought I was within some other host I don't care too much about instead and ran into a conflict by APT with the file mentioned in the subject. As I didn't care too much, I just kept it as is, but afterwards recognized that I was on the host, where I do care about how to properly solve those conflicts. The following is the output of APT I still have:
Code:
Setting up systemd-boot (257.8-1+pmx1) ...
Configuration file '/etc/initramfs/post-update.d/systemd-boot'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** systemd-boot (Y/I/N/O/D/Z) [default=N] ? d
--- /etc/initramfs/post-update.d/systemd-boot 2024-08-26 12:30:14.745235197 +0200
+++ /etc/initramfs/post-update.d/systemd-boot.dpkg-new 2025-08-04 22:43:18.000000000 +0200
@@ -1,15 +1,20 @@
#!/bin/sh
-# This hookfile has been disabled by proxmox-boot-tool
-exit 0
-#!/bin/sh
-
set -eu
test -x /usr/bin/bootctl || exit 0
bootctl is-installed --quiet || exit 0
+if [ -f "/boot/vmlinuz-$1" ]; then
+ k="/boot/vmlinuz-$1"
+elif [ -f "/boot/vmlinux-$1" ]; then
+ k="/boot/vmlinux-$1"
+else
+ echo "Kernel version $1 not found in /boot."
+ exit 0
+fi
+
echo "Updating kernel version $1 in systemd-boot..."
-kernel-install add "$1" "/boot/vmlinuz-$1" "$2"
+kernel-install add "$1" "$k" "$2"
Configuration file '/etc/initramfs/post-update.d/systemd-boot'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** systemd-boot (Y/I/N/O/D/Z) [default=N] ? n
Processing triggers for dbus (1.16.2-2) ...I can't remember to have ever executed proxmox-boot-tool in a way to trigger those changes. So I believe at some point some update or ... provided by the maintainer made that tool being called and changed that file. But then, the maintainer should have been aware of such a conflict most likely and would have addressed that already?!
Code:
root@srv01:/var/run# pveversion
pve-manager/9.0.6/49c767b70aeb6648 (running kernel: 6.14.11-1-pve)I had a look at the file APT kept and if I understand the code correct, the new and old file have the same safety checks and should gracefully not do anything, because "bootctl is-installed" would end with an error, making the script abort. But there's a reason most likely why theyx even changed it to hard-coded "exit 0" in the old version already.
So, how does that file needs to look like right now? Can I just put the new file from the maintainer into place?
Thanks!
