From: Andy Whitcroft <apw@canonical.com>
To: NoddingDog <lists@noddingdog.org>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
wireguard@lists.zx2c4.com, unit193@ubuntu.com
Subject: Re: Migrating From Ubuntu PPA to Real Ubuntu Packages
Date: Mon, 3 Aug 2020 22:18:38 +0100 [thread overview]
Message-ID: <20200803211838.GD6317@brain> (raw)
In-Reply-To: <5fe66967628e355831945a610f6804fdfd9a6928.camel@noddingdog.org>
On Mon, Aug 03, 2020 at 06:08:56PM +0200, NoddingDog wrote:
> Hello,
>
> I'd like to report a serious problem.
>
> I have a Dell XPS13 with Dell's OEM version of Ubuntu 18.04
>
> I had previously added the wireguard PPA and removed it as mentioned
> below.
>
> Now, when running sudo apt install wireguard, the system wants to
> install the following packages:
>
> linux-image-5.3.0-1032-gke
> linux-image-gke-5.3
> wireguard-tools
Yes, this is primarily a bug in the Depends on the wireguard package:
Depends: wireguard-modules (>= 0.0.20191219) | wireguard-dkms (>=
0.0.20200121-2), wireguard-tools (>= 1.0.20200513-1)
The linux-oem kernel has (separatly) a bug in its Provides so it does
not think it contains wireguard.ko. In that scenario we want the apt
resolver to pick wireguard-dkms as at least that way you have a
wireguard.ko. But the way it is formed it will pick wireguard-modules
for installation if neither is installed already. This can only be
solved by installing an unrelated kernel.
Am working on solving these problems variously.
-apw
next prev parent reply other threads:[~2020-08-03 21:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 10:28 Migrating From Ubuntu PPA to Real Ubuntu Packages Jason A. Donenfeld
2020-08-03 10:36 ` Jasper Knockaert
2020-08-03 11:42 ` Jason A. Donenfeld
2020-08-03 16:08 ` NoddingDog
2020-08-03 16:21 ` Jason A. Donenfeld
2020-08-03 16:25 ` NoddingDog
2020-08-03 16:28 ` Jason A. Donenfeld
2020-08-03 16:30 ` Jason A. Donenfeld
2020-08-03 16:43 ` NoddingDog
2020-08-03 16:47 ` Jason A. Donenfeld
2020-08-03 16:49 ` NoddingDog
[not found] ` <532c74129f32cffd53c71b87858929f800c2f87b.camel@noddingdog.org>
2020-08-03 16:42 ` Jason A. Donenfeld
2020-08-04 12:36 ` Andy Whitcroft
2020-08-04 13:26 ` Jason A. Donenfeld
2020-08-04 12:49 ` Andy Whitcroft
2020-08-04 13:14 ` Jason A. Donenfeld
2020-08-03 21:18 ` Andy Whitcroft [this message]
2020-08-03 21:24 ` Jason A. Donenfeld
2020-08-04 21:58 ` Jason A. Donenfeld
2020-08-05 6:23 ` NoddingDog
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=20200803211838.GD6317@brain \
--to=apw@canonical.com \
--cc=Jason@zx2c4.com \
--cc=lists@noddingdog.org \
--cc=unit193@ubuntu.com \
--cc=wireguard@lists.zx2c4.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.