From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH qemu-server] d/control: depend on EDK2 firmware package matching host, suggest others
Date: Mon, 18 May 2026 16:21:38 +0200 [thread overview]
Message-ID: <20260518142204.188374-1-f.ebner@proxmox.com> (raw)
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
debian/control | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/debian/control b/debian/control
index 149ae770..3ebab261 100644
--- a/debian/control
+++ b/debian/control
@@ -55,9 +55,10 @@ Depends: conntrack,
proxmox-termproxy (>= 2.1.0),
proxmox-websocket-tunnel,
pve-cluster,
+ pve-edk2-firmware-aarch64 [arm64],
# TODO: make legacy edk2 optional (suggests) for PVE 9 and warn explicitly about it
- pve-edk2-firmware-legacy | pve-edk2-firmware (<< 4~),
- pve-edk2-firmware-ovmf (>= 4.2025.05-2),
+ pve-edk2-firmware-legacy [amd64] | pve-edk2-firmware (<< 4~) [amd64],
+ pve-edk2-firmware-ovmf (>= 4.2025.05-2) [amd64],
pve-firewall (>= 6.0.3),
pve-ha-manager (>= 5.0.3),
pve-qemu-kvm (>= 7.1~),
@@ -71,7 +72,10 @@ Depends: conntrack,
Recommends: libpve-network-perl (>= 0.8.3),
proxmox-backup-file-restore (>= 2.1.9-2),
virtiofsd,
-Suggests: pve-edk2-firmware-aarch64, pve-edk2-firmware-riscv, proxmox-firewall (>= 1.1.1),
+Suggests: proxmox-firewall (>= 1.1.1),
+ pve-edk2-firmware-aarch64 [!arm64],
+ pve-edk2-firmware-ovmf [!amd64],
+ pve-edk2-firmware-riscv,
Breaks: pve-ha-manager (<< 4.0.1), pve-manager (<= 6.0-13),
Description: Qemu Server Tools
This package contains the Qemu Server tools used by Proxmox VE
--
2.47.3
next reply other threads:[~2026-05-18 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 14:21 Fiona Ebner [this message]
2026-05-18 20:06 ` applied: [PATCH qemu-server] d/control: depend on EDK2 firmware package matching host, suggest others Thomas Lamprecht
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=20260518142204.188374-1-f.ebner@proxmox.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.