From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-kernel] fix #3781: add Provides: wireguard-modules to control.in
Date: Fri, 10 Dec 2021 18:27:39 +0100 [thread overview]
Message-ID: <ef491912-cc69-a2e2-bc6d-1d13f659a3d1@proxmox.com> (raw)
In-Reply-To: <20211210164947.3138643-1-s.ivanov@proxmox.com>
On 10.12.21 17:49, Stoiko Ivanov wrote:
> 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
did we actually had users run into this? I'm probably way to accustomed to
just installing `wireguard-tools` that I never even noticed that there's a
meta package - I mean wireguard got mainlined with 5.6, that was released on
2020-01-26, so rather ancient ;-P
anyhow, lgtm
next prev parent reply other threads:[~2021-12-10 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 16:49 Stoiko Ivanov
2021-12-10 17:27 ` Thomas Lamprecht [this message]
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=ef491912-cc69-a2e2-bc6d-1d13f659a3d1@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@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.