From: Christian Hesse <list@eworm.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Arch Linux - out of date?!
Date: Wed, 25 Feb 2026 12:28:02 +0100 [thread overview]
Message-ID: <20260225122802.5e00abb4@leda.eworm.net> (raw)
In-Reply-To: <CAHmME9pnCLQCp=6=25fnV1jJcNQMeyrAaxLWTmAEOjDff-FkVw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 505 bytes --]
"Jason A. Donenfeld" <Jason@zx2c4.com> on Tue, 2026/02/24 13:27:
> I sorted out the arch and alpine ones, but there are still a bunch of
> others that are out of date or broken. For alpine I had to work around
> anubis (by using a curl useragent).
Thanks a lot!
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];)
putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-02-25 11:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 13:30 Arch Linux - out of date?! Christian Hesse
2026-02-10 13:45 ` Achill Gilgenast
2026-02-24 10:52 ` Christian Hesse
2026-02-24 10:57 ` Jason A. Donenfeld
2026-02-24 12:07 ` Christian Hesse
2026-02-24 12:27 ` Jason A. Donenfeld
2026-02-25 11:28 ` Christian Hesse [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=20260225122802.5e00abb4@leda.eworm.net \
--to=list@eworm.de \
--cc=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