From: David Anderson <dave@natulte.net>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: (Unofficial) wireguard packages for Debian Stretch (testing)
Date: Sat, 11 Feb 2017 01:49:36 -0800 [thread overview]
Message-ID: <CAMx+r7VgJ0xDAy46d28Qv_Vv7vM8JO0yRbYEh6AHVWT55LEVAw@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9q8+D7y0Hz4xOJv1MiVsq0=bUf3TgENseGEWWF2BEpx4Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]
On Sat, Feb 11, 2017 at 1:03 AM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> Mellow yellow,
>
> That's a great idea. Do you intend to track dkg's sid package more or
> less faithfully?
In that package repository, I intend to track the sid package exactly. If I
ever take up hacking on wireguard, I'll use a separate repository for any
modified versions.
If so, I'd be happy to advertise this on the
> wireguard.io/install/ page, since I'm sure a lot of people (including
> myself!) would benefit immensely from that.
>
Cool! I'll see about setting up debian stable as well.
> Could you send some bulletproof instructions -- 3 or 4 lines of
> commands like what's there currently -- and I'll put it on the site?
>
The instructions you have on there now are fine if you're okay with
packagecloud's shell script. Manual instructions that work are:
sudo apt-get install -y apt-transport-https linux-headers-amd64 curl
curl -L https://packagecloud.io/danderson/wireguard/gpgkey | sudo apt-key
add -
echo "deb https://packagecloud.io/danderson/wireguard/debian/ stretch main"
| sudo tee /etc/apt/sources.list.d/wireguard.list
sudo apt-get update
sudo apt-get install -y wireguard-dkms wireguard-tools
Note that right now, only amd64 packages are available. If you think
there's demand for Debian on 32-bit x86, I can set up i386 builders as well.
- Dave
> Thanks,
> Jason
>
[-- Attachment #2: Type: text/html, Size: 2602 bytes --]
next prev parent reply other threads:[~2017-02-11 9:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 0:23 David Anderson
2017-02-11 9:03 ` Jason A. Donenfeld
2017-02-11 9:49 ` David Anderson [this message]
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+r7VgJ0xDAy46d28Qv_Vv7vM8JO0yRbYEh6AHVWT55LEVAw@mail.gmail.com \
--to=dave@natulte.net \
--cc=Jason@zx2c4.com \
--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).