From: "Jason A. Donenfeld" <Jason@zx2c4.com> To: WireGuard mailing list <email@example.com> Cc: Jasper Knockaert <firstname.lastname@example.org>, Roman Mamedov <email@example.com>, Andy Whitcroft <firstname.lastname@example.org>, email@example.com, Joachim Lindenberg <firstname.lastname@example.org>, Daniel Kahn Gillmor <email@example.com> Subject: final call for Ubuntu 14.04 WireGuard support Date: Tue, 21 Jul 2020 15:12:14 +0200 [thread overview] Message-ID: <CAHmME9rckipsdZYW+LA=x6wCMybdFFA+VqoogFXnR=kHYiCteg@mail.gmail.com> (raw) Hi, As we speak, Canonical is finishing up their support for Ubuntu 16.04. That means WireGuard will be supported in their kernels and in their package repositories for Ubuntu 20.04, 19.10, 18.04, and 16.04. That means our PPA will only contain packages for Ubuntu 14.04. Ordinary support from Canonical (as well as public kernel sources) for 14.04 was EOL'd April 2019, over one year ago. Although there is technically support until April 2022, this is something that Canonical sells commercially, with those updates not released to the public (afaict). As well, my attempts to fix problems in the 14.04 kernel have been rejected, e.g. https://lists.ubuntu.com/archives/kernel-team/2020-May/110084.html . With our PPA soon only needing to support 14.04, and with Canonical not really supporting 14.04 for ordinary folks any more, I am leaning toward dropping our PPA, and 14.04 support with it, and marking our downstreaming efforts for Ubuntu integration as "complete". If you _are_ using WireGuard on Ubuntu 14.04 or know somebody who is, this would be the time to pipe up, so that we don't leave anyone hanging. Feel free to respond to this thread regarding ongoing WireGuard+14.04 usage and why updating your operating system isn't convenient, or send me an email privately if public disclosure of your infrastructure isn't an option. Thanks, Jason
next reply other threads:[~2020-07-21 13:12 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-21 13:12 Jason A. Donenfeld [this message] 2020-07-22 15:03 ` Jason A. Donenfeld 2020-10-07 11:15 ` Maykel Moya 2020-10-07 11:23 ` Jason A. Donenfeld 2021-12-13 14:10 ` Jason A. Donenfeld
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='CAHmME9rckipsdZYW+LA=x6wCMybdFFA+VqoogFXnR=kHYiCteg@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: final call for Ubuntu 14.04 WireGuard support' \ /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
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).