Hi DKG,
> Please make sure you can build the package from the debian/master branch
> at
https://salsa.debian.org/debian/wireguard> .
>
> If you can do that successfully (it shouldn't be too hard), feel free to
> take a look at the debian/TODO file, which contains a handful of
> suggestions, mos
Hi Willem--
On Tue 2019-10-01 06:50:29 +0200, Willem van den Akker wrote:
> I offer by help for maintaining packaging WG.
Thank you, happy to have help!
> Please let me know how I can help.
Please make sure you can build the package from the debian/master branch
at https://salsa.debian.org/deb
Hi Daniel,
I offer by help for maintaining packaging WG.
Please let me know how I can help.
/Willem
Daniel Kahn Gillmor wrote:
> Now, of course we could let it drop into testing for the moment by
> reducing the severity of this bug, and then cranking the severity back
> up before the release, but that feels a little bit like cheating, no?
>
> All that said, i do see the appeal of having wider di
Hi Georg--
On Wed 2017-07-12 02:56:45 +0200, Georg Faerber wrote:
> I would like to see wireguard right now in buster. Even if the on-wire
> format should change in the future, it would be still worth it, IMHO.
> Buster is the 'testing' suite - so let's just do that: let's test and
> get this int
Hi,
I would like to see wireguard right now in buster. Even if the on-wire
format should change in the future, it would be still worth it, IMHO.
Buster is the 'testing' suite - so let's just do that: let's test and
get this into testing. Sometimes testing breaks, which is expected, but
most of the
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, t
7 matches
Mail list logo
