From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-kernel] fix #3781: add Provides: wireguard-modules to control.in
Date: Fri, 10 Dec 2021 17:49:47 +0100 [thread overview]
Message-ID: <20211210164947.3138643-1-s.ivanov@proxmox.com> (raw)
without this line `apt install wireguard` pulls in Debian's kernel +
firmware which confilcts with pve-firmware - forcing users to install
via `apt install --no-install-recommends wireguard-tools` in order
to get the userspace utils.
For Debian's upstream kernel the linux-image-amd64 provides the
modules [0] - since pve-kernel-@KVNAME@ already provides linux-image
this should be the place where we add the provides
versioned dependency added since wireguard has a versioned dependency
on wireguard-modules.
[0] https://salsa.debian.org/kernel-team/linux/-/blob/master/debian/templates/control.image.meta.in
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
---
* quickly tested by building a kernel with this patch - installing it in a VM
and running `apt install wireguard` afterwards
debian/control.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/debian/control.in b/debian/control.in
index ee91978..fd8f4cb 100644
--- a/debian/control.in
+++ b/debian/control.in
@@ -59,7 +59,7 @@ Package: pve-kernel-@KVNAME@
Section: admin
Priority: optional
Architecture: any
-Provides: linux-image
+Provides: linux-image, wireguard-modules (= 1.0.0)
Suggests: pve-firmware
Depends: busybox, initramfs-tools
Recommends: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub-efi-arm64
@@ -68,7 +68,7 @@ Description: The Proxmox PVE Kernel Image
Package: pve-kernel-@KVNAME@-dbgsym
Architecture: any
-Provides: linux-debug
+Provides: linux-debug, wireguard-modules (= 1.0.0)
Section: devel
Priority: optional
Build-Profiles: <pkg.pve-kernel.debug>
--
2.30.2
next reply other threads:[~2021-12-10 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 16:49 Stoiko Ivanov [this message]
2021-12-10 17:27 ` Thomas Lamprecht
2021-12-10 17:33 ` Stoiko Ivanov
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=20211210164947.3138643-1-s.ivanov@proxmox.com \
--to=s.ivanov@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.