From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-kernel-meta/pve-kernel] add Provides for plain debian packages
Date: Mon, 13 Dec 2021 15:52:13 +0100 [thread overview]
Message-ID: <20211213145216.1603326-1-s.ivanov@proxmox.com> (raw)
This series results from an off-list discussion following
https://lists.proxmox.com/pipermail/pve-devel/2021-December/051178.html
Mostly the point was that adding a
`Provides: linux-headers-$(uname -r)-amd64` would help our users who
install various DKMS packages and don't expect our kernel headers
to be name pve-headers.
Since the patch already touches both pve-kernel and pve-kernel-meta I
decided to put the `Provides: wireguard-modules (=1.0.0)` in the
meta-package, following Debian upstream.
Tested:
* installing `proxmox-ve` on top of a plain debian VM - to check that this
still works smootly
* afterwards install `wireguard`
* running `apt install linux-headers-$(uname -r)-amd64`
pve-kernel-meta:
Stoiko Ivanov (2):
d/control.in: Provide linux-image/linux-headers
fix #3781: add Provides: wireguard-modules to control.in
debian/control.in | 2 ++
1 file changed, 2 insertions(+)
pve-kernel:
Stoiko Ivanov (1):
d/control.in: Provide versioned linux-image/linux-headers
debian/control.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
2.30.2
next reply other threads:[~2021-12-13 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 14:52 Stoiko Ivanov [this message]
2021-12-13 14:52 ` [pve-devel] [PATCH pve-kernel-meta 1/2] d/control.in: Provide linux-image/linux-headers Stoiko Ivanov
2021-12-13 14:52 ` [pve-devel] [PATCH pve-kernel-meta 2/2] fix #3781: add Provides: wireguard-modules to control.in Stoiko Ivanov
2021-12-13 14:52 ` [pve-devel] [PATCH pve-kernel 1/1] d/control.in: Provide versioned linux-image/linux-headers Stoiko Ivanov
2021-12-14 13:40 ` [pve-devel] applied-series: [PATCH pve-kernel-meta/pve-kernel] add Provides for plain debian packages Fabian Grünbichler
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=20211213145216.1603326-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox