From: Baptiste Jonglez <baptiste@bitsofnetworks.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Installation instructions for Debian
Date: Sat, 8 Jul 2017 16:14:02 +0200 [thread overview]
Message-ID: <20170708141402.GA13268@tuxmachine.polynome.dn42> (raw)
In-Reply-To: <CAHmME9o=EGWOcTRVtVQVCoJXL6KueX8eM98GWBJUtzEE67tAhw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1785 bytes --]
Hi again,
I think there is a small mistake in the installation instruction for
Debian, sorry about that: the "Pin-Priority" should be set to 150 instead
of 200.
Long explanation: on jessie, the jessie-backports repository also has a
priority of 200. After enabling unstable with the same priority, APT will
propose to upgrade all packages from jessie-backports to unstable, which
is probably not wanted nor expected.
Daniel, does that all make sense?
Baptiste
On Sun, May 14, 2017 at 12:58:37AM +0200, Jason A. Donenfeld wrote:
> Hey Baptiste,
>
> Spectacular, thanks a bunch. I think I had asked about this same thing
> a while back, but somehow I got confused in the ensuing mailing list
> thread and eventually I forgot about it. So I'm glad you've brought
> this back up. I updated the install page with verbatim what you sent.
>
> Jason
>
> On Sat, May 13, 2017 at 9:05 AM, Baptiste Jonglez
> <baptiste@bitsofnetworks.org> wrote:
> > Hi Jason,
> >
> > Could you update the installation instructions for Debian [1]?
> >
> > Based on the discussion from a few months ago, and given that Wireguard
> > now supports Jessie's 3.16 kernel, these instructions should be added:
> >
> > For Debian jessie or stretch:
> > # echo "deb http://deb.debian.org/debian/ unstable main" > /etc/apt/sources.list.d/unstable-wireguard.list
> > # cat <<EOF > /etc/apt/preferences.d/limit-unstable
> > Package: *
> > Pin: release a=unstable
> > Pin-Priority: 200
> > EOF
> > # apt update
> > # apt install wireguard-dkms wireguard-tools
> >
> > I have verified that the resulting setup is functional (with 0.0.20170421-2 on jessie).
> >
> > Thanks,
> > Baptiste
> >
> > [1] https://www.wireguard.io/install/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-08 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 7:05 Baptiste Jonglez
2017-05-13 22:58 ` Jason A. Donenfeld
2017-05-14 8:44 ` Baptiste Jonglez
2017-05-14 12:52 ` Daniel Kahn Gillmor
2017-07-08 14:14 ` Baptiste Jonglez [this message]
2017-07-10 0:50 ` Jason A. Donenfeld
2017-07-11 23:36 ` Daniel Kahn Gillmor
2017-07-12 0:00 ` Bzzzz
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=20170708141402.GA13268@tuxmachine.polynome.dn42 \
--to=baptiste@bitsofnetworks.org \
--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).