Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Silvan Nagl <mail@53c70r.de>
To: Jonathan Aquilina <jaquilina@eagleeyet.net>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Wireguard not available for CentOS Stream
Date: Wed, 6 Jan 2021 10:32:26 +0100	[thread overview]
Message-ID: <64e80310-cbb6-d972-6257-bfba53eea52e@53c70r.de> (raw)
In-Reply-To: <VE1PR08MB5837188C79F58A014916E123A0D10@53c70r.de>

I'm kinda amazed by Fedora Server at this point.
+1 for recommendation.

On 1/5/21 12:25 PM, Jonathan Aquilina wrote:
> Hi,
>
> Is Fedora a rolling release so to speak? I remember they used to call fedora the bleeding edge distro not really geared for production environments is that still accurate. I have only used it as a work station desktop with KDE installed.
>
> Regards,
> Jonathan
>
> -----Original Message-----
> From: WireGuard <wireguard-bounces@lists.zx2c4.com> On Behalf Of Jeffrey Walton
> Sent: 04 January 2021 22:55
> To: Jason A. Donenfeld <Jason@zx2c4.com>
> Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
> Subject: Re: Wireguard not available for CentOS Stream
>
> On Mon, Jan 4, 2021 at 7:48 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>> On Mon, Jan 4, 2021 at 2:24 AM Joe Doss <joe@solidadmin.com> wrote:
>>> https://copr.fedorainfracloud.org/coprs/jdoss/wireguard/
>>>
>>> The official DKMS install method for CentOS has a Stream repo 
>>> enabled. It should work fine. Let us know if you have any issues.
>> It's actually presently broken. I've fixed it in the master branch with:
>> https://git.zx2c4.com/wireguard-linux-compat/commit/?id=f7f55464a156e1
>> 181fa76d9c7e2fc0d495f2357e
>>
>> But Red Hat still has not fixed other bugs that will enable our CI to 
>> continue, and I won't release for RHEL alone until the CI is green.
>> You can cherry pick that into your dkms package if you need. I wrote 
>> Red Hat a patch and sent it, but there's been no updated kernel yet.
>>
>> More generally, I'm on the fence about how much I actually want to 
>> support CentOS Stream. CentOS non-Stream is annoying, because it's 
>> developed behind closed doors and is extremely slow to fix things, but 
>> at least the changes are gradual and it's easy to keep up with, by 
>> virtue of rarely changing. In contrast, CentOS Stream is fast moving, 
>> and extremely unstable, with builds frequently breaking. This would be 
>> fine and I would prefer it, since it means we can in theory get things 
>> fixed reasonably fast, but actually, Stream is still developed behind 
>> closed doors, with no visibility about what's going on, no 
>> communication from RH on when fixes are coming out, no regular or 
>> reliable release schedule, no releases for months sometimes, and just 
>> a bugzilla blackbox that forces all reports to be private/secret. So,
>> unstable+secretive development makes developing for CentOS Stream
>> nearly as fun as developing for macOS, which is to say, not very fun.
> From an admin and developer perspective I find Fedora Server a real gem. Speaking from experience, I would much rather work on Fedora than CentOS or Red Hat.  Fedora Server comes with the latest stable tools and does not need things like Software Collections (SCL) to get a modern Apache, Python or PHP.
>
> Every year or so Fedora Server needs a DNF System Upgrade (https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/),
> which is like a Ubuntu dist-upgrade. I've not had one go bad since I started using it back around F12 or F15.
>
> If Wireguard needs to make a Red Hat-family recommendation, I think it would be wise to consider Fedora Server.
>
> Jeff

  parent reply	other threads:[~2021-01-09  2:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-03 20:17 Silvan Nagl
2021-01-03 21:31 ` Silvan Nagl
2021-01-04  1:24 ` Joe Doss
2021-01-04 12:47   ` Jason A. Donenfeld
     [not found]     ` <CAL0FmdWzknetT9raQcr_BhJwSWSBKPxXZocHSr2TT6bz2QihSA@mail.gmail.com>
2021-01-04 19:42       ` Joe Doss
2021-01-04 20:25         ` Bruno Wolff III
2021-01-04 21:55     ` Jeffrey Walton
2021-01-05 11:25       ` Jonathan Aquilina
2021-01-05 18:35         ` Joe Doss
2021-01-05 18:14       ` Joe Doss
     [not found]       ` <VE1PR08MB5837188C79F58A014916E123A0D10@53c70r.de>
2021-01-06  9:32         ` Silvan Nagl [this message]
     [not found]     ` <CAH8yC8n-fC8MJxR7cA+otkqRyDZwhR7wz2Ni+-YTAgiKz7CRHA@53c70r.de>
2021-01-05 13:06       ` Silvan Nagl
2021-01-05 13:56         ` Jeffrey Walton
2021-01-05 14:58           ` Toke Høiland-Jørgensen
2021-01-12  9:57   ` Christopher Ng

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=64e80310-cbb6-d972-6257-bfba53eea52e@53c70r.de \
    --to=mail@53c70r.de \
    --cc=jaquilina@eagleeyet.net \
    --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).