Development discussion of WireGuard
 help / color / mirror / Atom feed
From: David Anderson <dave@natulte.net>
To: Baptiste Jonglez <baptiste@bitsofnetworks.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: (Unofficial) wireguard packages for Debian Stretch (testing)
Date: Sat, 11 Feb 2017 13:38:08 -0800	[thread overview]
Message-ID: <CAMx+r7VPbO5zvMYYnJ7anSf5fgg4Ofhr7V6Po-GazH1vFhVYkQ@mail.gmail.com> (raw)
In-Reply-To: <20170211162758.GA4633@tuxmachine.polynome.dn42>

[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]

On Sat, Feb 11, 2017 at 8:27 AM, Baptiste Jonglez <
baptiste@bitsofnetworks.org> wrote:

> On Sat, Feb 11, 2017 at 03:48:59AM -0800, David Anderson wrote:
> > Okay, I've set up a Debian stable builder as well... However, Debian
> stable
> > has a 3.16 kernel, and wireguard-dkms requires >=3.18, so installation
> > fails. Assuming 3.18 is a hard lower-bound on kernel versions, it looks
> > like jessie will never run in-kernel wireguard. Fortunately it'll be moot
> > in a few months when stretch becomes the new stable.
>
> Jessie-backports has linux 4.9, so it's probably much simpler to require
> users to install this.
>

Oh, excellent! I'll leave the jessie builder running then.

Jason: I'll get back to you once I've looked into setting up builds for
arm, to see how to revise the instructions. Given that each distro version
is likely to be slightly different, perhaps it'd be better to just link to
a readme on packagecloud.io, to avoid cluttering the install instructions
on wireguard.io?

- Dave


>
> > On Sat, Feb 11, 2017 at 2:17 AM, Jason A. Donenfeld <Jason@zx2c4.com>
> wrote:
> >
> > > Hi Dave,
> > >
> > > Ahh right, that old debate.
> > >
> > > Jason
> > >
>
> > _______________________________________________
> > WireGuard mailing list
> > WireGuard@lists.zx2c4.com
> > https://lists.zx2c4.com/mailman/listinfo/wireguard
>
>

[-- Attachment #2: Type: text/html, Size: 2327 bytes --]

  reply	other threads:[~2017-02-11 21:24 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 [this message]
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+r7VPbO5zvMYYnJ7anSf5fgg4Ofhr7V6Po-GazH1vFhVYkQ@mail.gmail.com \
    --to=dave@natulte.net \
    --cc=baptiste@bitsofnetworks.org \
    --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).