From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Andy Whitcroft <apw@canonical.com>
Cc: NoddingDog <lists@noddingdog.org>,
WireGuard mailing list <wireguard@lists.zx2c4.com>,
unit193@ubuntu.com
Subject: Re: Migrating From Ubuntu PPA to Real Ubuntu Packages
Date: Tue, 4 Aug 2020 15:14:32 +0200 [thread overview]
Message-ID: <CAHmME9py-TWnjhSPqjx_7BhVEqWaC-hVxp_1ToTbZORsToBJsw@mail.gmail.com> (raw)
In-Reply-To: <20200804124942.GF6317@brain>
On Tue, Aug 4, 2020 at 2:49 PM Andy Whitcroft <apw@canonical.com> wrote:
>
> On Mon, Aug 03, 2020 at 06:25:51PM +0200, NoddingDog wrote:
> > I'm sure I did apt update after removing the PPA, but just checked
> > again:
> >
> > apt update
> > apt install wireguard
> >
> > Same result - those gke kernels are included as dependencies and "will
> > be installed".
> >
> > Maybe Dell need to fix their bionic-oem repositories?
>
> The breakage here came from bad dependancies on the Debian wireguard
> packages which we backported to these series. They incorrectly (for
> Ubuntu) depend primarily on wireguard-modules which triggers an actual
> dependancy on a kernel package; a severe no-no for exactly the issue
> hit here. It should likely have been caught in review but was not.
>
> New packages are in the review queue and expected in -proposed today
> across the board. They will be released as soon as is practicle.
The breakage is because you forgot the Provides: in the oem-meta
package. Debian's ordering of the Depends: just helped unearth the
problem, as explained in a message yesterday.
next prev parent reply other threads:[~2020-08-04 13:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 10:28 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 [this message]
2020-08-03 21:18 ` Andy Whitcroft
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=CAHmME9py-TWnjhSPqjx_7BhVEqWaC-hVxp_1ToTbZORsToBJsw@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=apw@canonical.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).