Your message dated Sun, 08 Sep 2019 16:28:52 -0400
with message-id <87y2yy5y7v....@fifthhorseman.net>
and subject line Re: Bug#849308: state of wireguard mainline inclusion?
has caused the Debian Bug report #849308,
regarding wireguard: Wireguard should not transition to stable yet
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
849308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wireguard
Version: 0.0.20161223-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Wireguard appears to be stable and reliable enough to distribute in
debian unstable, to get more widespread testing than would arise from
distribution in experimental alone.
However, the on-wire format might still change, leading to potential
interop issues, and upstream isn't yet willing to maintain a stable
branch in the face of security issues (which is understandable given
the age of the project.
So this bug report is a placeholder to keep it from migration. Feel
free to comment here!
--dkg
-- System Information:
Debian Release: stretch/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing'), (200,
'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 0.0.20190905-1
Over in 849...@bugs.debian.org, Daniel Kahn Gillmor wrote:
> I do plan for putting wireguard into buster-backports, since i expect
> the upstream inclusion issues to be resolved one way or another by the
> time of bullseye release. If anyone wants to help out by adding it to
> stretch-backports-sloppy, i would welcome that.
Following up on this, and after some discussion with Jason (upstream), i
think it's time to let wireguard migrate into debian testing.
So i'm closing #849308 with this e-mail, and once wireguard migrates
into testing, i'll look into putting it into buster-backports.
I welcome anyone who wants to contribute to the debian packaging to
offer maintenance help too!
--dkg
signature.asc
Description: PGP signature
--- End Message ---
