Github messages for voidlinux
 help / color / mirror / Atom feed
From: zen0bit <zen0bit@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] scrcpy: Update to 2.3.1
Date: Wed, 10 Jan 2024 03:44:30 +0100	[thread overview]
Message-ID: <20240110024430.BmV9ACgwX2POIWllpyKmzrx4l43cAMayDFRAZIBcEBU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47926@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 473 bytes --]

There is an updated pull request by zen0bit against master on the void-packages repository

https://github.com/oSoWoSo/VUR scrcpy
https://github.com/void-linux/void-packages/pull/47926

scrcpy: Update to 2.3.1

#### Testing the changes
- I tested the changes in this PR: **briefly**

#### Local build testing
- I built this PR locally for my native architecture, (x64 glibc)


A patch file from https://github.com/void-linux/void-packages/pull/47926.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-scrcpy-47926.patch --]
[-- Type: text/x-diff, Size: 1218 bytes --]

From 5162474baaeb434a54fee0af441b76242743112f Mon Sep 17 00:00:00 2001
From: zenobit <zenobit@disroot.org>
Date: Wed, 27 Dec 2023 19:16:21 +0100
Subject: [PATCH] scrcpy: Update to 2.3.1

---
 srcpkgs/scrcpy/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/scrcpy/template b/srcpkgs/scrcpy/template
index ac18bc03418ce..d04de770dc191 100644
--- a/srcpkgs/scrcpy/template
+++ b/srcpkgs/scrcpy/template
@@ -1,6 +1,6 @@
 # Template file for 'scrcpy'
 pkgname=scrcpy
-version=2.1.1
+version=2.3.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="6f3d055159cb125eabe940a901bef8a69e14e2c25f0e47554f846e7f26a36c4d
- 9558db6c56743a1dc03b38f59801fb40e91cc891f8fc0c89e5b0b067761f148e"
+checksum="76f38779f00d91d0b46a399ebca32c82ff1facdbd843871b7e46c2e7cad38a42
+ f6814822fc308a7a532f253485c9038183c6296a6c5df470a9e383b4f8e7605b"
 skip_extraction="scrcpy-server-v${version}"
 
 post_install() {

  reply	other threads:[~2024-01-10  2:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-27 18:18 [PR PATCH] " zen0bit
2024-01-10  2:44 ` zen0bit [this message]
2024-02-10  9:59 ` adigitoleo
2024-02-15 17:41 ` [PR PATCH] [Merged]: " 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=20240110024430.BmV9ACgwX2POIWllpyKmzrx4l43cAMayDFRAZIBcEBU@z \
    --to=zen0bit@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).