On the [install page of the website](https://www.wireguard.com/install/), the 
default pin config smartly deprioritizes Sid after adding the repository. 
However, it seems this causes the wireguard packages to be non-upgradable. 
After speaking with someone on IRC about this, I can't think of a reason why we 
wouldn't want to be able to upgrade the wireguard packages. So, I'd like to 
propose the following addition to the pinning configuration written in the 
instructions (unified diff follows):


--- orig        2019-09-07 08:43:08.489455140 -0400
+++ new 2019-09-07 08:45:49.056137802 -0400
@@ -1,4 +1,4 @@
# echo "deb http://deb.debian.org/debian/ unstable main" > 
-# printf 'Package: *\nPin: release a=unstable\nPin-Priority: 90\n' > 
+# printf 'Package: *\nPin: release a=unstable\nPin-Priority: 90\n\nPackage: 
/^wireguard/\nPin: release a=unstable\nPin-Priority: 500\n' > 
# apt update
# apt install wireguard


This preserves the general priority of 90 for *, but it also sets any package 
starting with wireguard to 500, which matches the default priority used in the 

The only reason I chose a regex match here is in case any additional wireguard 
packages get added later, other than wireguard, wireguard-dkms, and 
wireguard-tools. Otherwise, the Package line could read:

Package: wireguard wireguard-dkms wireguard-tools

Anyone have any objections to this approach? Also, is there a repo for the 
website I can fork and PR this to?

Thank you in advance.

Salvatore LaMendola

WireGuard mailing list

Reply via email to