From: sirkhancision <sirkhancision@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] syncplay: update to 1.7.0.
Date: Tue, 04 Apr 2023 22:30:52 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43271@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
There is a new pull request by sirkhancision against master on the void-packages repository
https://github.com/sirkhancision/void-packages syncplay
https://github.com/void-linux/void-packages/pull/43271
syncplay: update to 1.7.0.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
- I built this PR locally for these architectures:
- aarch64
- i686
- x86_64-musl
A patch file from https://github.com/void-linux/void-packages/pull/43271.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-syncplay-43271.patch --]
[-- Type: text/x-diff, Size: 1107 bytes --]
From 9efae5ddfc6d97314c679bb9ca15d40c80cae6c5 Mon Sep 17 00:00:00 2001
From: sirkhancision <jsantiago12tone@gmail.com>
Date: Mon, 3 Apr 2023 00:12:40 -0300
Subject: [PATCH] syncplay: update to 1.7.0.
---
srcpkgs/syncplay/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/syncplay/template b/srcpkgs/syncplay/template
index bb34277a9106..53ac7cbbb36f 100644
--- a/srcpkgs/syncplay/template
+++ b/srcpkgs/syncplay/template
@@ -1,7 +1,7 @@
# Template file for 'syncplay'
pkgname=syncplay
-version=1.6.9
-revision=3
+version=1.7.0
+revision=1
build_style=gnu-makefile
pycompile_dirs="usr/lib/syncplay/syncplay"
depends="desktop-file-utils python3-pyside2 python3-Twisted
@@ -11,7 +11,7 @@ maintainer="KeepBotting <branon.mcclellan@gmail.com>"
license="Apache-2.0"
homepage="https://syncplay.pl/"
distfiles="https://github.com/syncplay/syncplay/archive/v${version}.tar.gz"
-checksum=b4acaf009b816dcb3261d9b327aace9005494f0977944b65e3623d50eb465972
+checksum=d65c402869a5b5906a601cb08452363d29d7f08a4e5df0edd29676d8c0c7b81d
python_version=3
post_install() {
next reply other threads:[~2023-04-04 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 20:30 sirkhancision [this message]
2023-04-05 18:40 ` [PR PATCH] [Updated] " sirkhancision
2023-04-11 18:40 ` sirkhancision
2023-04-13 0:03 ` [PR REVIEW] " classabbyamp
2023-04-13 0:21 ` [PR PATCH] [Updated] " sirkhancision
2023-04-13 0:32 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43271@inbox.vuxu.org \
--to=sirkhancision@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).