Development discussion of WireGuard
 help / color / mirror / Atom feed
From: NoddingDog <lists@noddingdog.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: wireguard@lists.zx2c4.com, unit193@ubuntu.com, apw@canonical.com
Subject: Re: Migrating From Ubuntu PPA to Real Ubuntu Packages
Date: Mon, 03 Aug 2020 18:25:51 +0200	[thread overview]
Message-ID: <d7506c2b3a5dce1c8c6c37c352f3ee50f6eed414.camel@noddingdog.org> (raw)
In-Reply-To: <CAHmME9oLOSwC4_55cUZpHoXU+m8L=QQ20aDcn-ia5sWxQ+3nDA@mail.gmail.com>

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?


On Mon, 2020-08-03 at 18:21 +0200, Jason A. Donenfeld wrote:
> On Mon, Aug 3, 2020 at 6:15 PM NoddingDog <lists@noddingdog.org>
> 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
> > 
> > These kernel images are **completely wrong** for the laptop (they
> > are
> > Google Container Engine kernel images). I didn't notice and borked
> > my
> > system by installing them. I had to load an old kernel and purge
> > them
> > before my system would work properly again.
> > 
> > Maybe this needs fixing before too many other folks have the same
> > problem.
> 
> Try running `apt update` first, and please let me know if that fixes
> the issue.
> 
> IIRC, Andy (CC'd as apw@) initially ported WireGuard to 18.04 with a
> package bug, which he later rectified.
> 
> Jason


  reply	other threads:[~2020-08-03 16:26 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 [this message]
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
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=d7506c2b3a5dce1c8c6c37c352f3ee50f6eed414.camel@noddingdog.org \
    --to=lists@noddingdog.org \
    --cc=Jason@zx2c4.com \
    --cc=apw@canonical.com \
    --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).