From: daniel-eys <daniel-eys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] scrcpy: update to 2.1.1.
Date: Sat, 15 Jul 2023 12:19:58 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45050@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]
There is a new pull request by daniel-eys against master on the void-packages repository
https://github.com/daniel-eys/void-packages scrcpy
https://github.com/void-linux/void-packages/pull/45050
scrcpy: update to 2.1.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, (ARCH-LIBC)
- 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/45050.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-scrcpy-45050.patch --]
[-- Type: text/x-diff, Size: 1243 bytes --]
From aac86287d29c5a61cefe6523c00d53ec992c06ab Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Daniel=20Ey=C3=9Fer?= <daniel.eysser@gmail.com>
Date: Sat, 15 Jul 2023 01:41:43 +0200
Subject: [PATCH] scrcpy: update to 2.1.1.
---
srcpkgs/scrcpy/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/scrcpy/template b/srcpkgs/scrcpy/template
index 06208c389ca9..ac18bc03418c 100644
--- a/srcpkgs/scrcpy/template
+++ b/srcpkgs/scrcpy/template
@@ -1,6 +1,6 @@
# Template file for 'scrcpy'
pkgname=scrcpy
-version=2.1
+version=2.1.1
revision=1
build_style=meson
configure_args="-Dcompile_server=false
@@ -14,8 +14,8 @@ license="Apache-2.0"
homepage="https://github.com/Genymobile/scrcpy"
distfiles="https://github.com/Genymobile/scrcpy/archive/v${version}.tar.gz
https://github.com/Genymobile/scrcpy/releases/download/v${version}/scrcpy-server-v${version}"
-checksum="57a277238d19d3471f37003d0d567bb8cde0a2b487b5cf91416129b463d9e8d5
- 5b8bf1940264b930c71a1c614c57da2247f52b2d4240bca865cc6d366dff6688"
+checksum="6f3d055159cb125eabe940a901bef8a69e14e2c25f0e47554f846e7f26a36c4d
+ 9558db6c56743a1dc03b38f59801fb40e91cc891f8fc0c89e5b0b067761f148e"
skip_extraction="scrcpy-server-v${version}"
post_install() {
next reply other threads:[~2023-07-15 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 10:19 daniel-eys [this message]
2023-07-16 15:17 ` [PR PATCH] [Merged]: " Duncaen
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-45050@inbox.vuxu.org \
--to=daniel-eys@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).