From: mvf <mvf@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] protonvpn-cli: update to 2.2.12 (fixes connection)
Date: Thu, 14 Mar 2024 10:25:11 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49284@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
There is a new pull request by mvf against master on the void-packages repository
https://github.com/mvf/void-packages pr/protonvpn-cli
https://github.com/void-linux/void-packages/pull/49284
protonvpn-cli: update to 2.2.12 (fixes connection)
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
---
Fixes connection failing with:
```
[!] There was an error with accessing the ProtonVPN API.
[!] Please make sure your connection is working properly!
[!] HTTP Error Code: 422
```
A patch file from https://github.com/void-linux/void-packages/pull/49284.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pr/protonvpn-cli-49284.patch --]
[-- Type: text/x-diff, Size: 1158 bytes --]
From 26f085abf7fe31ca0923f71309387ed172058a5c Mon Sep 17 00:00:00 2001
From: Matthias von Faber <mvf@gmx.eu>
Date: Wed, 13 Mar 2024 16:41:47 +0100
Subject: [PATCH] protonvpn-cli: update to 2.2.12
---
srcpkgs/protonvpn-cli/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/protonvpn-cli/template b/srcpkgs/protonvpn-cli/template
index 20fd9d1f495ee2..ccb0deb47f53f0 100644
--- a/srcpkgs/protonvpn-cli/template
+++ b/srcpkgs/protonvpn-cli/template
@@ -1,7 +1,7 @@
# Template file for 'protonvpn-cli'
pkgname=protonvpn-cli
-version=2.2.11
-revision=5
+version=2.2.12
+revision=1
build_style=python3-module
hostmakedepends="python3-setuptools"
makedepends="python3-devel"
@@ -12,5 +12,5 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-3.0-or-later"
homepage="https://github.com/Rafficer/linux-cli-community"
distfiles="https://github.com/Rafficer/linux-cli-community/archive/refs/tags/v${version}.tar.gz"
-checksum=2fc643762e9156928b706c31a7826427a7ca12c7ae4cdfb656746cd2de3af66b
+checksum=586b34fb87ad0823fc24643c7b460acef517da4257b1330c9064009ec1215168
make_check=no # Package Defines No Checks
next reply other threads:[~2024-03-14 9:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 9:25 mvf [this message]
2024-06-13 1:48 ` github-actions
2024-06-13 13:42 ` [PR PATCH] [Updated] " mvf
2024-06-16 23:09 ` [PR PATCH] [Closed]: " classabbyamp
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-49284@inbox.vuxu.org \
--to=mvf@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).