From: NoddingDog <lists@noddingdog.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Migrating From Ubuntu PPA to Real Ubuntu Packages
Date: Mon, 03 Aug 2020 18:43:26 +0200 [thread overview]
Message-ID: <2bf53aa68644d0595c76db514a5aca769a13f25f.camel@noddingdog.org> (raw)
In-Reply-To: <CAHmME9oTLHTfRw+_QAqqZNb4=GCb1WnJaEBsm_tBhzJ7FzoFkA@mail.gmail.com>
Good you've found the issue.
That'll teach me to be an early adopter... ;-)
On Mon, 2020-08-03 at 18:30 +0200, Jason A. Donenfeld wrote:
> On Mon, Aug 3, 2020 at 6:28 PM Jason A. Donenfeld <Jason@zx2c4.com>
> wrote:
> >
> > On Mon, Aug 3, 2020 at 6:25 PM NoddingDog <lists@noddingdog.org>
> > 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?
> >
> > Ooof, that sounds disastrous. Hopefully Andy is reading these
> > emails
> > and will fix this issue, but I'll poke him on IRC too.
> >
> > Could you send me the URLs for the repos your laptop is using? I'd
> > like to double check the Release files on there. Perhaps just the
> > contents of /etc/apt or similar, and the name of the kernel package
> > your system uses?
>
> Bingo:
>
> zx2c4@bionicman:~$ apt-cache show linux-image-oem | grep Provides
> zx2c4@bionicman:~$ apt-cache show linux-image-generic | grep Provides
> Provides: wireguard-modules (= 1.0.20200611-1ubuntu1~18.04.1),
> zfs-modules (= 0.7.5-1ubuntu16.9)
>
> Indeed looks like maybe this was left out of linux-image-oem? That's
> surprising, especially given the trials and tribulations we went
> through initially to get this deployed to Dell customers.
next prev parent reply other threads:[~2020-08-03 16:44 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 [this message]
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
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=2bf53aa68644d0595c76db514a5aca769a13f25f.camel@noddingdog.org \
--to=lists@noddingdog.org \
--cc=Jason@zx2c4.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).