wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Georg Faerber <georg@riseup.net>
To: wireguard@lists.zx2c4.com
Subject: Re: FYI: systemd's networkd (v242) incorrectly setting listen-port on wg interface
Date: Mon, 2 Sep 2019 22:41:25 +0000	[thread overview]
Message-ID: <20190902224125.GH1480@debian> (raw)
In-Reply-To: <CAMx+r7WOqTnHf0uXixM-8WO2WyyfRX=dZ1WszDnMKgy+Epfaug@mail.gmail.com>

Hi,

On 19-09-02 12:42:00, David Anderson wrote:
> Seems to be known to Debian:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936198 . I'm not
> super familiar with Debian's development process, but I _think_, from
> that bug + the systemd debian repo's state, that the fix is now
> submitted and pending upload to unstable, after which it should flow
> backwards over time into Buster.

That's only partially correct, and maybe the following is nitpicking,
but at least wanted to ensure this is known:

The fix is pending upload to unstable, and will hit testing soon after.
Expect this for the upcoming days. However, as buster is stable, it will
not "automatically" flow into buster. This needs proposing an targeted
update to the Stable Release Managers and an ACK by them -- which would
probably be granted due to the severity. If you want this to happen,
it's probably a good idea to tell the maintainer, so he knows people
would be happy if this gets fixed in buster as well.

Cheers,
Georg
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2019-09-02 22:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02 19:26 FYI: systemd's networkd (v242) incorrectly setting listen-port on wg interface David Anderson
2019-09-02 19:42 ` David Anderson
2019-09-02 22:41   ` Georg Faerber [this message]
2019-09-02 22:46     ` David Anderson
2019-09-02 22:51       ` Georg Faerber
2019-09-02 23:25   ` David Anderson

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=20190902224125.GH1480@debian \
    --to=georg@riseup.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).