From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: build breakage on Ubuntu 19.10
Date: Wed, 19 Feb 2020 21:32:15 +0100 [thread overview]
Message-ID: <CAHmME9rAVrEUsRibMJ30UBJbsYfD4FaAcpcqmSGR4JMvJ2=_bw@mail.gmail.com> (raw)
Hi all,
The Canonical kernel team is a bit behind in deploying fixes (i.e.
bumping the wireguard package version) for recent breakage they
introduced. As a result, WireGuard will entirely stop working when
people update their systems. It's been like this for at least a week,
as far as I can see, and the emails keep piling up, so it seems
prudent I send a warning about the issue.
As an interim fix, Unit193 very nicely got our usual PPA making
packages for Ubuntu 19.10, which you can use in place of the packages
from Canonical. To activate this, do the following:
$ sudo add-apt-repository ppa:wireguard/wireguard
$ sudo apt-get update
$ sudo apt-get upgrade
That should result in updating your wireguard package from Canonical's
to the working and up to date one inside of the PPA.
Sorry about this. For 20.04 LTS, Canonical will be shipping wireguard
along with their kernel, and we've also discussed them doing the same
for 18.04 LTS. This means that it'll be built as part of their CI and
distributed normally, so problems like this shouldn't come up again.
And of course, with WireGuard being upstream now, as Linux 5.6
trickles down into the distros, this class of problems should
disappear entirely.
Regards,
Jason
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2020-02-19 20:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAHmME9rAVrEUsRibMJ30UBJbsYfD4FaAcpcqmSGR4JMvJ2=_bw@mail.gmail.com' \
--to=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).