From: David Anderson <dave@natulte.net>
To: wireguard@lists.zx2c4.com
Subject: (Unofficial) wireguard packages for Debian Stretch (testing)
Date: Fri, 10 Feb 2017 16:23:50 -0800 [thread overview]
Message-ID: <CAMx+r7WsvfJ6j7JT9+Z5mNe=FEFwehTVNgX+7-8vnQMa5FxORg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1205 bytes --]
next reply other threads:[~2017-02-11 0:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 0:23 David Anderson [this message]
2017-02-11 9:03 ` Jason A. Donenfeld
2017-02-11 9:49 ` David Anderson
2017-02-11 10:04 ` Jason A. Donenfeld
2017-02-11 10:15 ` David Anderson
2017-02-11 10:17 ` Jason A. Donenfeld
2017-02-11 11:48 ` David Anderson
2017-02-11 13:28 ` Jason A. Donenfeld
2017-02-11 16:27 ` Baptiste Jonglez
2017-02-11 21:38 ` David Anderson
2017-02-11 12:32 ` Jason A. Donenfeld
2017-02-11 21:36 ` David Anderson
2017-02-12 2:40 ` David Anderson
2017-02-12 13:42 ` Jason A. Donenfeld
2017-02-12 23:01 ` Daniel Kahn Gillmor
2017-02-12 23:37 ` Jason A. Donenfeld
2017-02-14 4:55 ` David Anderson
2017-02-14 15:50 ` Daniel Kahn Gillmor
2017-02-15 21:31 ` Baptiste Jonglez
2017-02-17 2:46 ` Daniel Kahn Gillmor
2017-02-17 8:15 ` Baptiste Jonglez
2017-02-17 13:32 ` Jason A. Donenfeld
2017-02-17 3:14 ` David Anderson
2017-02-17 19:49 ` Daniel Kahn Gillmor
2017-02-20 23:53 ` David Anderson
2017-02-21 0:53 ` Ibrahim Tachijian
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+r7WsvfJ6j7JT9+Z5mNe=FEFwehTVNgX+7-8vnQMa5FxORg@mail.gmail.com' \
--to=dave@natulte.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).