Development discussion of WireGuard
 help / color / mirror / Atom feed
From: NoddingDog <lists@noddingdog.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>, wireguard@lists.zx2c4.com
Cc: unit193@ubuntu.com, apw@canonical.com
Subject: Re: Migrating From Ubuntu PPA to Real Ubuntu Packages
Date: Mon, 03 Aug 2020 18:08:56 +0200	[thread overview]
Message-ID: <5fe66967628e355831945a610f6804fdfd9a6928.camel@noddingdog.org> (raw)
In-Reply-To: <20200803102808.GA1402387@zx2c4.com>

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.

BR



On Mon, 2020-08-03 at 12:28 +0200, Jason A. Donenfeld wrote:
> Hi folks,
> 
> At long last, Ubuntu now supports WireGuard on releases 20.04, 19.10,
> 18.04, and 16.04, which means we've got all currently supported LTS
> releases covered. For that reason, we're in the process of sunsetting
> the PPA that previously provided packages to some users. This email
> details possible changes users might consider.
> 
> The right way to install WireGuard on Ubuntu now consists of a single
> command:
> 
>     $ sudo apt install wireguard
> 
> This "wireguard" package will *automatically* pull in either one or
> two
> packages with it:
> 
>   1) wireguard-tools: this will always be pulled in and provides
> wg(8)
>      and wg-quick(8).
>   2) wireguard-dkms: this will only be pulled in if your kernel
> doesn't
>      already come with WireGuard.
> 
> As suggested by (2), most Ubuntu kernels now come with WireGuard out
> of
> the box, even older releases, to which WireGuard has been backported.
> This is great news and will result in much better reliability during
> upgrades, as well as smoother compatibility with SecureBoot. You can
> learn if your Ubuntu kernel comes with WireGuard out of the box by
> running this command:
> 
> zx2c4@bionicman:~$ dpkg --get-selections | grep -v deinstall | cut -f
> 1 | grep linux-image | xargs apt-cache show | grep ^Provides: | grep
> wireguard-modules
> Provides: wireguard-modules (= 1.0.20200611-1ubuntu1~18.04.1), zfs-
> modules (= 0.7.5-1ubuntu16.9)
> 
> Or alternatively:
> 
> zx2c4@bionicman:~$ ls -l /lib/modules/$(uname
> -r)/kernel/wireguard/wireguard.ko
> -rw-r--r-- 1 root root 286985 Jul  9 23:13 /lib/modules/4.15.0-112-
> generic/kernel/wireguard/wireguard.ko
> 
> If those messages are *not* printed, then it simply means that your
> Ubuntu kernel does not (yet) come with WireGuard out of the box, in
> which case, the above "sudo apt install wireguard" command will
> *automatically* install wireguard-dkms along with it.
> 
> Users should never need to manually install wireguard-tools or
> wireguard-dkms. Rather, *only* install the "wireguard" package, and
> this
> will automatically choose the correct additional packages to pull in.
> 
> For those who previously used the PPA, if the above commands indicate
> that your kernel *does* come with WireGuard, then you'll probably
> want
> to *remove* the wireguard-dkms package if it has not already been
> automatically removed:
> 
>     $ sudo apt remove wireguard-dkms
> 
> As well, all previous users of the PPA may remove it:
> 
>    $ sudo add-apt-repository --remove ppa:wireguard/wireguard
> 
> From this point forward, all updates will be handled by Canonical
> from
> the main Ubuntu package repositories. No PPAs are needed.
> 
> Hopefully this process should be fairly smooth. Most users have
> already
> had Canonical-blessed WireGuard installed for some time now, so it
> should be fairly smooth sailing.
> 
> Let me know if you have any questions.
> 
> Regards,
> Jason
> 
> PS: In case you missed the announcement from two weeks ago, we intend
> to sunset support for Ubuntu 14.04 in the PPA, and afterwards remove
> the
> PPA itself:
> - https://lists.zx2c4.com/pipermail/wireguard/2020-July/005670.html
> - https://data.zx2c4.com/sunset-wg-14.04.gif


  parent reply	other threads:[~2020-08-03 16:21 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 [this message]
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
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=5fe66967628e355831945a610f6804fdfd9a6928.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).