From: ipkalm <ipkalm@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] v2ray: update to 5.2.1
Date: Mon, 16 Jan 2023 09:39:54 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41677@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]
There is a new pull request by ipkalm against master on the void-packages repository
https://github.com/ipkalm/void-packages v2ray-5.2.1_1
https://github.com/void-linux/void-packages/pull/41677
v2ray: update to 5.2.1
<!-- 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, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- x86_64-musl
- i686
- i686-musl
- aarch64
- aarch64-musl
- armv7l
- armv7l-musl
- armv6l
- armv6l-musl
- ppc64le
A patch file from https://github.com/void-linux/void-packages/pull/41677.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-v2ray-5.2.1_1-41677.patch --]
[-- Type: text/x-diff, Size: 1111 bytes --]
From 1304a8e4a60b9f07d17edf891121fe4c5d9d022e Mon Sep 17 00:00:00 2001
From: ipkalm <ipkalm@outlook.com>
Date: Mon, 16 Jan 2023 15:36:24 +0700
Subject: [PATCH] v2ray: update to 5.2.1
---
srcpkgs/v2ray/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/v2ray/template b/srcpkgs/v2ray/template
index ba6fcb1bf11a..300d28896d32 100644
--- a/srcpkgs/v2ray/template
+++ b/srcpkgs/v2ray/template
@@ -1,7 +1,7 @@
# Template file for 'v2ray'
pkgname=v2ray
-version=5.1.0
-revision=2
+version=5.2.1
+revision=1
build_style=go
go_import_path="github.com/v2fly/v2ray-core/v5"
go_ldflags="-X github.com/v2fly/v2ray-core/v5.codename=$pkgname
@@ -12,7 +12,7 @@ maintainer="ipkalm <ipkalm@outlook.com>"
license="MIT"
homepage="https://github.com/v2fly/v2ray-core"
distfiles="https://github.com/v2fly/v2ray-core/archive/v${version}/${pkgname}-${version}.tar.gz"
-checksum=b3dbd2bbee9486999b81d1968545c5a6caa7b0f4726a7259939f1bda54fcf5ea
+checksum=97bc872e798fed51c23c39f8f63ee25984658e2b252b0ec2c8ec469c00a4d77a
conf_files="/etc/v2ray/config.json"
system_accounts="_v2ray"
next reply other threads:[~2023-01-16 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 8:39 ipkalm [this message]
2023-01-21 16:29 ` [PR PATCH] [Merged]: " ahesford
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-41677@inbox.vuxu.org \
--to=ipkalm@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).