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 18:40:43 -0800 [thread overview]
Message-ID: <CAMx+r7Xk+vVwLq++8gnn1GfSA=jvYr=nM0EaLUjdvHXbjWD1kQ@mail.gmail.com> (raw)
In-Reply-To: <CAMx+r7WMmcGxDLE7Dt2w6S5xj0tx3U22T-HQBhss1SzV0pgbiQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
I'm failing at setting up arm builds, raspbian/rpi emulation is not in a
great shape these days. In the meantime, debian stable for amd64 is up.
Updated instructions for both debian versions are at
https://packagecloud.io/danderson/wireguard#readme-scrollto . In
particular, the jessie install requires first installing a backported
kernel. I'll keep poking at arm builds for a bit, but I don't promise
anything.
- Dave
On Sat, Feb 11, 2017 at 1:36 PM, David Anderson <dave@natulte.net> wrote:
> On Sat, Feb 11, 2017 at 4:32 AM, Jason A. Donenfeld <Jason@zx2c4.com>
> wrote:
>
>> Hey Dave,
>>
>> On Sat, Feb 11, 2017 at 10:49 AM, David Anderson <dave@natulte.net>
>> wrote:
>> > 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.
>>
>> I doubt anybody cares about i386, but likely armv{6,7} and arm64 are
>> in demand somewhat, at the very least due to Rasberrian users.
>>
>
> Hmm, I don't have functional arm-ish things on hand, but I'll see what I
> can do with emulated setups. I'll skip i386 for now, if it turns out to be
> in demand it's one VM spinup away.
>
>
>> Jason
>>
>
>
[-- Attachment #2: Type: text/html, Size: 2227 bytes --]
next prev parent reply other threads:[~2017-02-12 2:27 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
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 [this message]
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+r7Xk+vVwLq++8gnn1GfSA=jvYr=nM0EaLUjdvHXbjWD1kQ@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).