From: David Anderson <dave@natulte.net>
To: Georg Faerber <georg@riseup.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: FYI: systemd's networkd (v242) incorrectly setting listen-port on wg interface
Date: Mon, 2 Sep 2019 15:46:24 -0700 [thread overview]
Message-ID: <CAMx+r7V-HDW9yZ+LDKq0NuE+V9LpX3hs_y5_TVKN66tqWkvMSA@mail.gmail.com> (raw)
In-Reply-To: <20190902224125.GH1480@debian>
On Mon, Sep 2, 2019 at 3:42 PM Georg Faerber <georg@riseup.net> wrote:
>
> 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.
Thanks for the correction! I tried to figure out how stuff gets into
stable, but my quick research didn't reveal an obvious standard
method.
So the way to go about this is to ping the maintainer of the systemd
package out of band? Or file a bug on Debian's bugtracker? I'm still
not sure how to kick off this process.
Cheers,
- Dave
>
> Cheers,
> Georg
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-09-02 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 19:26 David Anderson
2019-09-02 19:42 ` David Anderson
2019-09-02 22:41 ` Georg Faerber
2019-09-02 22:46 ` David Anderson [this message]
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=CAMx+r7V-HDW9yZ+LDKq0NuE+V9LpX3hs_y5_TVKN66tqWkvMSA@mail.gmail.com \
--to=dave@natulte.net \
--cc=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).