Development discussion of WireGuard
 help / color / mirror / Atom feed
From: NoddingDog <lists@noddingdog.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>,
	Andy Whitcroft <apw@canonical.com>,
	W.Jackson@dell.com, unit193@ubuntu.com
Subject: Re: Migrating From Ubuntu PPA to Real Ubuntu Packages
Date: Mon, 03 Aug 2020 18:49:58 +0200	[thread overview]
Message-ID: <d45090e8a80c9324e1c57ae71b33171588176318.camel@noddingdog.org> (raw)
In-Reply-To: <CAHmME9raRNgM3+NPjpF4aPQpH9VUYNkrg=h9zUwb0jVfBgx=ZQ@mail.gmail.com>

On Mon, 2020-08-03 at 18:47 +0200, Jason A. Donenfeld wrote:
> On Mon, Aug 3, 2020 at 6:43 PM NoddingDog <lists@noddingdog.org>
> wrote:
> > 
> > Good you've found the issue.
> > 
> > That'll teach me to be an early adopter... ;-)
> 
> Sigh. Sorry you're having that experience with WireGuard. Usually
> things go quite a bit better with the WireGuard side of things, but
> this seems pretty par for the course with _Ubuntu_ and Canonical's
> kernel team. We've had perpetual issues over the last 6 months with
> getting Canonical to release high quality packages in a timely
> manner.
> A pretty large portion of my time is spent dealing with these bugs
> and
> Ubuntu in general. I'm hoping they can finally get their stuff worked
> out and support users properly, and I had hoped that everything was
> *finally* in order today, but it seems like it was not meant to be.
> Problems continue, alas. I've poked Andy on IRC and hopefully we can
> get fixes for this deployed as soon as their procedures and paperwork
> allow.

"Sorry you're having that experience with WireGuard."

No hard feelings at all... I'm using it extensively and this is the
first time I've had any problems with wireguard. Keep up the good work!


  reply	other threads:[~2020-08-03 16:50 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 [this message]
     [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=d45090e8a80c9324e1c57ae71b33171588176318.camel@noddingdog.org \
    --to=lists@noddingdog.org \
    --cc=Jason@zx2c4.com \
    --cc=W.Jackson@dell.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).