From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] [WIP] wireguard-dkms: Attempt to prevent install on linux>=5.6
Date: Thu, 30 Jul 2020 03:05:10 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23937@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
There is a new pull request by cinerea0 against master on the void-packages repository
https://github.com/cinerea0/void-packages wireguard
https://github.com/void-linux/void-packages/pull/23937
[WIP] wireguard-dkms: Attempt to prevent install on linux>=5.6
In [a recent issue I opened](https://github.com/void-linux/void-packages/issues/23790), I brought up that it was confusing whether or not wireguard-dkms was needed. The package's description now states that it's only for kernel versions 5.5 and lower, but I'd like to outright prevent someone from trying to install it on a kernel where it's not necessary. This is my attempt to do that.
A patch file from https://github.com/void-linux/void-packages/pull/23937.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-wireguard-23937.patch --]
[-- Type: text/x-diff, Size: 910 bytes --]
From f020205dfe1d3c8a2c569b1ace7a360c97e51b99 Mon Sep 17 00:00:00 2001
From: cinerea0 <cinerea0@protonmail.com>
Date: Wed, 29 Jul 2020 21:01:03 -0400
Subject: [PATCH] wireguard-dkms: Attempt to prevent install on linux>=5.6
---
srcpkgs/wireguard-dkms/template | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/srcpkgs/wireguard-dkms/template b/srcpkgs/wireguard-dkms/template
index a21066ff2f5..77b474e0f5c 100644
--- a/srcpkgs/wireguard-dkms/template
+++ b/srcpkgs/wireguard-dkms/template
@@ -1,10 +1,11 @@
# Template file for 'wireguard-dkms'
pkgname=wireguard-dkms
version=1.0.20200729
-revision=1
+revision=2
wrksrc="wireguard-linux-compat-${version}"
build_wrksrc="src"
depends="dkms wireguard-tools perl"
+conflicts="linux>=5.6"
short_desc="Fast, modern, secure VPN tunnel (DKMS module for Linux <= 5.5)"
maintainer="Leah Neukirchen <leah@vuxu.org>"
license="GPL-2.0-only"
next reply other threads:[~2020-07-30 1:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 1:05 cinerea0 [this message]
2020-07-30 1:24 ` ericonr
2020-07-30 1:33 ` cinerea0
2020-07-30 2:15 ` sgn
2020-07-30 2:20 ` ericonr
2020-07-30 2:26 ` cinerea0
2020-07-30 2:26 ` [PR PATCH] [Closed]: " cinerea0
2020-07-30 20:04 ` ericonr
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23937@inbox.vuxu.org \
--to=cinerea0@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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).