Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Baptiste Jonglez <baptiste@bitsofnetworks.org>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Installation instructions for Debian
Date: Tue, 11 Jul 2017 19:36:02 -0400	[thread overview]
Message-ID: <87mv8ay2al.fsf@fifthhorseman.net> (raw)
In-Reply-To: <20170708141402.GA13268@tuxmachine.polynome.dn42>

On Sat 2017-07-08 16:14:02 +0200, Baptiste Jonglez wrote:

> 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?

Yep, that sounds reasonable to me.  fwiw, apt_preferences(5) indicates
what the different cutoffs for priorities are, and explains why
jessie-backports defaults to something in the 200 range ("NotAutomatic:
yes" and "ButAutomaticUpgrades: yes"), and 150 should still have the
same properties (it's above 100, but below 500).

     --dkg

  parent reply	other threads:[~2017-07-11 23:28 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
2017-07-10  0:50     ` Jason A. Donenfeld
2017-07-11 23:36     ` Daniel Kahn Gillmor [this message]
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=87mv8ay2al.fsf@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=Jason@zx2c4.com \
    --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).