From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: [pve-devel] applied: [PATCH proxmox-kernel-helper] systemd-boot: switch to suggesting new packages
Date: Fri, 1 Aug 2025 10:52:50 +0200 [thread overview]
Message-ID: <477bc619-849e-47e6-ae55-85b987c8d46d@proxmox.com> (raw)
In-Reply-To: <20250731114455.995999-1-f.gruenbichler@proxmox.com>
Am 31.07.25 um 13:45 schrieb Fabian Grünbichler:
> in Trixie, systemd-boot got split into:
>
> systemd-boot: systemd integration and automatic installation of bootloader
> systemd-boot-tools: bootctl
> systemd-boot-efi(-XXX-signed): EFI binaries
>
> when managed using p-b-t, we only want the latter two, since systemd-boot fails
> its postinst (sometimes) if the ESP is not mounted.
>
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
> ---
>
> Notes:
> we prepared a fixed systemd-boot package for our repositories, but since
> systemd is updated fairly frequently even in Debian stable we either need to
> keep doing that or avoid pulling in systemd-boot on p-b-t *using* systems..
>
> but of course, users might want to use systemd-boot without p-b-t, so a hard
> Conflict also seems like a bad option..
>
> debian/control | 2 +-
> src/bin/proxmox-boot-tool | 6 +++++-
> 2 files changed, 6 insertions(+), 2 deletions(-)
>
>
applied this one already yesterday, thanks!
_______________________________________________
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-01 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 11:44 [pve-devel] " Fabian Grünbichler
2025-08-01 8:52 ` Thomas Lamprecht [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=477bc619-849e-47e6-ae55-85b987c8d46d@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.gruenbichler@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