From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: [pve-devel] superseded: [PATCH manager v2] 8 to 9 checks: do not ask bootctl if systemd-boot is used.
Date: Thu, 7 Aug 2025 22:31:59 +0200 [thread overview]
Message-ID: <20250807223159.6722e37e@rosa.proxmox.com> (raw)
In-Reply-To: <86af5762-5b31-4000-8180-5ea64103b442@proxmox.com>
Thanks big-time for the feedback on- and off-list!
sent an updated v3:
https://lore.proxmox.com/pve-devel/20250807203004.336616-1-s.ivanov@proxmox.com/T/#t
On Thu, 7 Aug 2025 14:29:34 +0200
Fiona Ebner <f.ebner@proxmox.com> wrote:
> Am 06.08.25 um 1:03 PM schrieb Stoiko Ivanov:
> > get systemd-boot installed to /boot/efi upon upgrade
>
> What problems does this cause (except for the false positive)? Can/do
> users need to do something to recover? If yes, I think we should have
> the script output more information.
>
> > @@ -1624,18 +1624,11 @@ sub check_bootloader {
> > }
> > } else {
> > if (-f "/usr/share/doc/systemd-boot/changelog.Debian.gz") {
> > - my $exit_code = eval {
> > - run_command(['bootctl', 'is-installed', '--quiet', '--graceful'], noerr => 1);
> > - };
> > - if ($exit_code != 0) {
> > - log_warn(
> > - "systemd-boot meta-package installed but the system does not seem to use it"
> > - . " for booting. This can cause problems on upgrades of other boot-related packages."
> > - . " Consider removing 'systemd-boot'");
> > - } else {
> > - log_info("systemd-boot used as bootloader and fitting meta-package installed.");
> > - return;
> > - }
> > + log_warn(
> > + "systemd-boot meta-package installed. This can cause problems on upgrades of other"
> > + ." boot-related packages. Unless you manually setup the system to use"
> > + ." systemd-boot remove 'systemd-boot'");
> > + return;
>
> Note that we did not return in the 'if' branch previously, which means
> the next check below won't be done anymore. Is that intentional? It
> seems like it should be done.
>
> > }
> > if (!-f "/usr/share/doc/grub-efi-amd64/changelog.Debian.gz") {
> > log_warn("System booted in uefi mode but grub-efi-amd64 meta-package not installed,"
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-08-07 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 11:02 [pve-devel] " Stoiko Ivanov
2025-08-07 12:29 ` Fiona Ebner
2025-08-07 20:31 ` Stoiko Ivanov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250807223159.6722e37e@rosa.proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox