public inbox for wireguard@lists.zx2c4.com
 help / color / mirror / Atom feed
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: Tue, 24 Feb 2026 13:07:51 +0100	[thread overview]
Message-ID: <20260224130751.1faee59a@leda.eworm.net> (raw)
In-Reply-To: <CAHmME9pf=TNw6S6HB48q3NKhHzNLAo4qxH64Y7i8Lgg6etFCsg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]

"Jason A. Donenfeld" <Jason@zx2c4.com> on Tue, 2026/02/24 11:57:
> On Tue, Feb 24, 2026 at 11:53 AM Christian Hesse <list@eworm.de> wrote:
> >
> > Christian Hesse <list@eworm.de> on Tue, 2026/02/10 14:30:  
> > > Hello everybody,
> > >
> > > for some time already I am annoyed by mails clogging my input regarding
> > > wireguard-tools for Arch Linux being out of date. Obviously this is not
> > > true, I built the package the day of release. [0]
> > >
> > > Now found the install page mentioning the package being out-of date...
> > > [1] What goes wrong and how to fix that?
> > >
> > > [0] https://archlinux.org/packages/extra/x86_64/wireguard-tools/
> > > [1] https://www.wireguard.com/install/#arch-module-tools  
> >
> > Ping... I would like to see this resolved.
> >
> > Alternatively I will set up my mail server to forward these mails to you
> > personally, Jason.  
> 
> Hehe.
> 
> In the midst of a big infrastructure refresh (as perhaps you've
> noticed), so this is certainly in the queue there. Sorry about this.

Ok, will wait patiently then. Just wanted to make sure this is not lost. :)

Is the code available in git anywhere? I could have a look myself then.
-- 
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 --]

  reply	other threads:[~2026-02-24 12:08 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 [this message]
2026-02-24 12:27       ` Jason A. Donenfeld
2026-02-25 11:28         ` Christian Hesse

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=20260224130751.1faee59a@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