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: Wed, 05 Aug 2020 08:23:08 +0200 [thread overview]
Message-ID: <fcca32ed88b1c2533123edef505127e5e8b53b94.camel@noddingdog.org> (raw)
In-Reply-To: <CAHmME9qeZ5bSFToFoQZqiNQpwNyHp+25T9Nzhu+cR=7s+oGR1w@mail.gmail.com>
On Tue, 2020-08-04 at 23:58 +0200, Jason A. Donenfeld wrote:
> Hey NoddingDog,
>
> I think that the fix has now been released to -updates, as of about
> 20
> minutes ago. It may still take some time to hit the mirrors, but can
> you see if "apt update && apt upgrade && apt install wireguard"
> produces a saner result than last time?
>
> Thanks to Andy for getting this fixed so quickly!
>
> Jason
OK, I tried again and this time the following packages were offered:
linux-headers-oem
linux-image-oem
linux-oem
wireguard tools
Installed, rebooted and all seems fine. Thanks all for the fix!
prev parent reply other threads:[~2020-08-05 6:23 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
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 [this message]
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=fcca32ed88b1c2533123edef505127e5e8b53b94.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).