From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: dave@natulte.net Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 9adf0b6d for ; Sat, 11 Feb 2017 00:10:28 +0000 (UTC) Received: from mail-vk0-f45.google.com (mail-vk0-f45.google.com [209.85.213.45]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id a6044a3c for ; Sat, 11 Feb 2017 00:10:27 +0000 (UTC) Received: by mail-vk0-f45.google.com with SMTP id t8so36796700vke.3 for ; Fri, 10 Feb 2017 16:24:13 -0800 (PST) MIME-Version: 1.0 From: David Anderson Date: Fri, 10 Feb 2017 16:23:50 -0800 Message-ID: Subject: (Unofficial) wireguard packages for Debian Stretch (testing) To: wireguard@lists.zx2c4.com Content-Type: multipart/alternative; boundary=001a11415e88b6df330548363b05 List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --001a11415e88b6df330548363b05 Content-Type: text/plain; charset=UTF-8 Mellow greetings, In case it's of use to anyone, I've built wireguard packages for Debian testing. I wanted to play with wireguard on my Debian Stretch systems, but wireguard is currently locked to Sid only until 1.0 brings API stability guarantees. So, I set up a cronjob that rebuilds the Sid source package on a Stretch system, and the result is wireguard packages that track the latest release, but don't pull in unstable versions of libc and whatnot when you try to install them, as would happen if you tried to install via package pinning. Naturally, you have only my word that the packages are unmodified rebuilds of Debian's original package, and you're trusting packagecloud to not tamper with the packages (it's their signing keys, not mine) so caveat emptor. It works for me, it might work for you as well. With the warnings and disclaimers out of the way, here's the repo: https://packagecloud.io/danderson/wireguard?filter=debs - Dave --001a11415e88b6df330548363b05 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Mellow greetings,

In case it= 's of use to anyone, I've built wireguard packages for Debian testi= ng. I wanted to play with wireguard on my Debian Stretch systems, but wireg= uard is currently locked to Sid only until 1.0 brings API stability guarant= ees.

So, I set up a cronjob that rebuilds the Sid = source package on a Stretch system, and the result is wireguard packages th= at track the latest release, but don't pull in unstable versions of lib= c and whatnot when you try to install them, as would happen if you tried to= install via package pinning.

Naturally, you have = only my word that the packages are unmodified rebuilds of Debian's orig= inal package, and you're trusting packagecloud to not tamper with the p= ackages (it's their signing keys, not mine) so caveat emptor. It works = for me, it might work for you as well.

With the wa= rnings and disclaimers out of the way, here's the repo:=C2=A0https://package= cloud.io/danderson/wireguard?filter=3Ddebs

- D= ave
--001a11415e88b6df330548363b05--