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, W.Jackson@dell.com
Subject: Re: Migrating From Ubuntu PPA to Real Ubuntu Packages
Date: Tue, 4 Aug 2020 15:26:17 +0200 [thread overview]
Message-ID: <CAHmME9pqn_=Ui3CJnF3r=cyjpJN1zNYD=0v=Kczr5kUKhZjJsw@mail.gmail.com> (raw)
In-Reply-To: <20200804123658.GE6317@brain>
On Tue, Aug 4, 2020 at 2:37 PM Andy Whitcroft <apw@canonical.com> wrote:
>
> On Mon, Aug 03, 2020 at 06:42:49PM +0200, Jason A. Donenfeld wrote:
> > Looks like we're all set for these kernels:
> >
> > zx2c4@bionicman:~$ apt-cache show linux-image-* | grep -C5 "^Source: linux-meta" | grep -B10 "^Provides: .*wireguard-modules" | grep ^Package:
> > Package: linux-image-generic
> > Package: linux-image-aws
> > Package: linux-image-azure
> > Package: linux-image-azure-edge
> > Package: linux-image-gcp
> > Package: linux-image-kvm
> > Package: linux-image-lowlatency
> > Package: linux-image-virtual
> > Package: linux-image-aws-edge
> > Package: linux-image-aws-lts-18.04
> > Package: linux-image-gcp-edge
> > Package: linux-image-generic-hwe-18.04
> > Package: linux-image-generic-hwe-18.04-edge
> > Package: linux-image-gke-5.4
> > Package: linux-image-lowlatency-hwe-18.04
> > Package: linux-image-lowlatency-hwe-18.04-edge
> > Package: linux-image-oracle
> > Package: linux-image-oracle-edge
> > Package: linux-image-virtual-hwe-18.04
> > Package: linux-image-virtual-hwe-18.04-edge
> > Package: linux-image-gke-5.3
> >
> > But we are not all set for these kernels:
> >
> > zx2c4@bionicman:~$ comm -23 <(apt-cache show linux-image-* | grep -C5 "^Source: linux-meta" | grep ^Package: | sort | uniq) <(apt-cache show linux-image-* | grep -C5 "^Source: linux-meta" | grep -B10 "^Provides: .*wireguard-modules" | grep ^Package: | sort | uniq)
> > Package: linux-image-azure-lts-18.04
> > Package: linux-image-extra-virtual
> > Package: linux-image-extra-virtual-hwe-16.04
> > Package: linux-image-extra-virtual-hwe-16.04-edge
> > Package: linux-image-extra-virtual-hwe-18.04
> > Package: linux-image-extra-virtual-hwe-18.04-edge
> > Package: linux-image-gcp-lts-18.04
> > Package: linux-image-generic-hwe-16.04
> > Package: linux-image-generic-hwe-16.04-edge
> > Package: linux-image-gke
> > Package: linux-image-gke-4.15
> > Package: linux-image-gke-5.0
> > Package: linux-image-gkeop-5.3
> > Package: linux-image-gkeop-5.4
> > Package: linux-image-lowlatency-hwe-16.04
> > Package: linux-image-lowlatency-hwe-16.04-edge
> > Package: linux-image-oem
> > Package: linux-image-oem-osp1
> > Package: linux-image-oracle-lts-18.04
> > Package: linux-image-virtual-gkeop-5.0
> > Package: linux-image-virtual-hwe-16.04
> > Package: linux-image-virtual-hwe-16.04-edge
> >
> > Appears that the "oem" kernel is part of the bad list.
>
> This list is somewhat inaccurate as about half of those are transitional
> packages an not expected to actually have provides. linux-oem is
> unfortuantly converted but misses its linux-meta-oem changes. This is
> being sorted out. The remaining are being reviewed.
Thanks for clarifying. So we're now certain about linux-meta-oem (aka
Dell's kernel) being broken. Could you keep the list updated if you're
able to confirm that others are broken too?
Jason
next prev parent reply other threads:[~2020-08-04 13:27 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 [this message]
2020-08-04 12:49 ` Andy Whitcroft
2020-08-04 13:14 ` Jason A. Donenfeld
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='CAHmME9pqn_=Ui3CJnF3r=cyjpJN1zNYD=0v=Kczr5kUKhZjJsw@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=W.Jackson@dell.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).