From: HadetTheUndying <HadetTheUndying@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] protonvpn-cli: change to new upstream
Date: Wed, 20 May 2020 06:05:12 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22145@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
There is a new pull request by HadetTheUndying against master on the void-packages repository
https://github.com/HadetTheUndying/void-packages protonvpn-upstreamchange
https://github.com/void-linux/void-packages/pull/22145
protonvpn-cli: change to new upstream
ProtonVPN's upstream address changed, I have updated the template to make packaging it in the future less of a headache for the next release.
A patch file from https://github.com/void-linux/void-packages/pull/22145.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-protonvpn-upstreamchange-22145.patch --]
[-- Type: text/x-diff, Size: 1444 bytes --]
From 3c1eac1be7442c3dde0d688d6cb97e296ee23d3d Mon Sep 17 00:00:00 2001
From: HadetTheUndying <hadet@protonmail.com>
Date: Tue, 19 May 2020 23:01:45 -0500
Subject: [PATCH] protonvpn-cli: change to new upstream
---
srcpkgs/protonvpn-cli/template | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/protonvpn-cli/template b/srcpkgs/protonvpn-cli/template
index 2f9d1035da2..a0dd8310635 100644
--- a/srcpkgs/protonvpn-cli/template
+++ b/srcpkgs/protonvpn-cli/template
@@ -1,9 +1,9 @@
# Template file for 'protonvpn-cli'
pkgname=protonvpn-cli
version=2.2.2
-revision=1
+revision=2
archs=noarch
-wrksrc="${pkgname}-ng-${version}"
+wrksrc="linux-cli-${version}"
build_style=python3-module
hostmakedepends="python3-setuptools"
makedepends="python3-devel"
@@ -11,6 +11,6 @@ depends="openvpn python3-pythondialog python3-docopt python3-requests"
short_desc="Linux command-line client for ProtonVPN written in Python"
maintainer="svenper <svenper@tuta.io>"
license="GPL-3.0-or-later"
-homepage="https://github.com/ProtonVPN/protonvpn-cli-ng"
-distfiles="https://github.com/ProtonVPN/protonvpn-cli-ng/archive/v${version}.tar.gz"
-checksum=c6aec40b40602f0d577097728cacd2080c2206da04625d707ab4a39ba9c2153a
+homepage="https://github.com/ProtonVPN/linux-cli"
+distfiles="https://github.com/ProtonVPN/linux-cli/archive/v${version}.tar.gz"
+checksum=7d4d8c10e8c05626a17bfc901b287b847944ae1c0d09859ef6c3992c924a114f
next reply other threads:[~2020-05-20 4:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 4:05 HadetTheUndying [this message]
2020-05-20 7:19 ` Piraty
2020-05-20 7:19 ` Piraty
2020-05-20 18:45 ` [PR PATCH] [Updated] " HadetTheUndying
2020-05-20 19:40 ` [PR PATCH] [Merged]: " Hoshpak
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-22145@inbox.vuxu.org \
--to=hadettheundying@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).