From: rakino <rakino@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] proxychains-ng: update to 4.15.
Date: Tue, 07 Dec 2021 04:54:38 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34415@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]
There is a new pull request by rakino against master on the void-packages repository
https://github.com/rakino/void-packages patch-2
https://github.com/void-linux/void-packages/pull/34415
proxychains-ng: update to 4.15.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
<!--
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/34415.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-2-34415.patch --]
[-- Type: text/x-diff, Size: 1075 bytes --]
From 636cec8b432687c54fe8dc88499a1d97bbf17fbb Mon Sep 17 00:00:00 2001
From: Hilton Chain <26847027+rakino@users.noreply.github.com>
Date: Tue, 7 Dec 2021 11:52:33 +0800
Subject: [PATCH] proxychains-ng: update to 4.15.
---
srcpkgs/proxychains-ng/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/proxychains-ng/template b/srcpkgs/proxychains-ng/template
index 4f9cfa8f74e6..3cbb9a335e93 100644
--- a/srcpkgs/proxychains-ng/template
+++ b/srcpkgs/proxychains-ng/template
@@ -1,6 +1,6 @@
# Template file for 'proxychains-ng'
pkgname=proxychains-ng
-version=4.14
+version=4.15
revision=1
build_style=gnu-configure
make_install_target="install install-config"
@@ -10,4 +10,4 @@ maintainer="David <kalichakra@zoho.com>"
license="GPL-2.0-only"
homepage="https://github.com/rofl0r/proxychains-ng"
distfiles="http://ftp.barfooze.de/pub/sabotage/tarballs/${pkgname}-${version}.tar.xz"
-checksum=9d00e035b8a808b9e0c750501b08f38eeadd0be421f30ee83e88fd15e872b0ae
+checksum=3207ab7f1f053c3fdcdf5ac158bcdef0683e3b7d8427b602ce9c0abe6a369081
next reply other threads:[~2021-12-07 3:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 3:54 rakino [this message]
2021-12-11 3:17 ` [PR PATCH] [Merged]: " ericonr
-- strict thread matches above, loose matches on Subject: below --
2021-08-27 14:17 [PR PATCH] " ailiop-git
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-34415@inbox.vuxu.org \
--to=rakino@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).