wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Laszlo KERTESZ <laszlo.kertesz@gmail.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Debian unstable Pin-Priority too high in Installation documentation
Date: Sun, 11 Nov 2018 04:56:28 +0200	[thread overview]
Message-ID: <CANcuY=rLL1mX2FLHgL6z2fDcrRE9pbHT50MnOcEi8TsGGWDo+w@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1489 bytes --]

Hi,
On the Wireguard site the Debian installation Pin-Priority is at 150 - this
is too high because the official Backports (Stretch-Backports currently)
has a default of 100. This makes certain packages such as kernel images to
be pointed to Unstable instead of Backports.
I believe a number such as 90 should be better choice.

For example for the package linux-image-amd64 we have:

# apt-cache policy linux-image-amd64
linux-image-amd64:
  Installed: 4.18+98~bpo9+1
  Candidate: 4.18+99
  Version table:
     4.18+99 150
        150 http://deb.debian.org/debian unstable/main amd64 Packages
 *** 4.18+98~bpo9+1 100
        100 http://ftp.debian.org/debian stretch-backports/main amd64
Packages
        100 /var/lib/dpkg/status
     4.9+80+deb9u6 500
        500 http://ftp.debian.org/debian stretch/main amd64 Packages
        500 http://security.debian.org/debian-security stretch/updates/main
amd64 Packages

But if we lower the Pin Priority to 90:

# apt-cache policy linux-image-amd64
linux-image-amd64:
  Installed: 4.18+98~bpo9+1
  Candidate: 4.18+98~bpo9+1
  Version table:
     4.18+99 90
         90 http://deb.debian.org/debian unstable/main amd64 Packages
 *** 4.18+98~bpo9+1 100
        100 http://ftp.debian.org/debian stretch-backports/main amd64
Packages
        100 /var/lib/dpkg/status
     4.9+80+deb9u6 500
        500 http://ftp.debian.org/debian stretch/main amd64 Packages
        500 http://security.debian.org/debian-security stretch/updates/main
amd64 Packages

[-- Attachment #1.2: Type: text/html, Size: 2269 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

             reply	other threads:[~2018-11-11  2:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-11  2:56 Laszlo KERTESZ [this message]
2018-11-12  3:55 ` Debian unstable Pin-Priority too high in Installation documentation Jason A. Donenfeld
2018-11-12  8:16   ` Laszlo KERTESZ
2018-11-12 10:07 ` Daniel Kahn Gillmor
2018-11-13  1:21   ` Jason A. Donenfeld

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='CANcuY=rLL1mX2FLHgL6z2fDcrRE9pbHT50MnOcEi8TsGGWDo+w@mail.gmail.com' \
    --to=laszlo.kertesz@gmail.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).