From: octeep <octeep@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] wireproxy: update to 1.0.5
Date: Thu, 01 Sep 2022 06:11:39 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39016@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
There is a new pull request by octeep against master on the void-packages repository
https://github.com/octeep/void-packages master
https://github.com/void-linux/void-packages/pull/39016
wireproxy: update to 1.0.5
<!-- 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 [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
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, amd64
A patch file from https://github.com/void-linux/void-packages/pull/39016.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-39016.patch --]
[-- Type: text/x-diff, Size: 1230 bytes --]
From a042dfd616d223e0d20eaa51376cc4cf7f64466a Mon Sep 17 00:00:00 2001
From: BuildTools <unconfigured@null.spigotmc.org>
Date: Thu, 1 Sep 2022 12:02:15 +0800
Subject: [PATCH] wireproxy: update to 1.0.5
---
srcpkgs/wireproxy/template | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/wireproxy/template b/srcpkgs/wireproxy/template
index 984027a4f69e..15ff49dc0d12 100644
--- a/srcpkgs/wireproxy/template
+++ b/srcpkgs/wireproxy/template
@@ -1,16 +1,17 @@
# Template file for 'wireproxy'
pkgname=wireproxy
-version=1.0.1
+version=1.0.5
revision=1
build_style=go
go_import_path="github.com/octeep/wireproxy"
go_package="${go_import_path}/cmd/wireproxy"
+go_ldflags="-X 'main.version=${version}'"
short_desc="Wireguard client that exposes itself as a socks5 proxy"
maintainer="Wind Wong <octeep@pm.me>"
license="ISC"
homepage="https://github.com/octeep/wireproxy"
distfiles="https://github.com/octeep/wireproxy/archive/v${version}.tar.gz"
-checksum=e21eac22ef1b12dc2d7b3e5b58dcff183af9c1547be3e55a7e6c71394f053e1e
+checksum=3779a157713b462a7b5322f1437f768ab69ae446df0ceca76c6dff7c4030e425
make_dirs="
/etc/wireproxy 0750 root _wireproxy
/var/lib/wireproxy 0700 _wireproxy _wireproxy"
next reply other threads:[~2022-09-01 4:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 4:11 octeep [this message]
2022-09-02 9:22 ` classabbyamp
2022-09-02 12:49 ` [PR PATCH] [Updated] " octeep
2022-09-02 16:01 ` [PR PATCH] [Merged]: " paper42
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-39016@inbox.vuxu.org \
--to=octeep@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).