From: kshade <kshade@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-mpv: update to 1.0.6.
Date: Sun, 28 Apr 2024 13:52:54 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50097@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 522 bytes --]
There is a new pull request by kshade against master on the void-packages repository
https://github.com/kshade/void-packages master
https://github.com/void-linux/void-packages/pull/50097
python3-mpv: update to 1.0.6.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
Bump because mpv-0.38.0_1 broke python3-mpv-1.0.3_2
A patch file from https://github.com/void-linux/void-packages/pull/50097.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-50097.patch --]
[-- Type: text/x-diff, Size: 1122 bytes --]
From a50c3d0f90fce5367b74ca3d46636eb75e7d04cc Mon Sep 17 00:00:00 2001
From: kshade <kshade@crct.de>
Date: Sun, 28 Apr 2024 13:34:23 +0200
Subject: [PATCH] python3-mpv: update to 1.0.6.
---
srcpkgs/python3-mpv/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/python3-mpv/template b/srcpkgs/python3-mpv/template
index eb94673d7ca188..e27010fe155f95 100644
--- a/srcpkgs/python3-mpv/template
+++ b/srcpkgs/python3-mpv/template
@@ -1,7 +1,7 @@
# Template file for 'python3-mpv'
pkgname=python3-mpv
-version=1.0.3
-revision=2
+version=1.0.6
+revision=1
build_style=python3-pep517
# this test takes too long and has a low chance of failure
# https://github.com/jaseg/python-mpv/issues/209#issuecomment-1180248112
@@ -14,4 +14,4 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-2.0-or-later"
homepage="https://github.com/jaseg/python-mpv"
distfiles="https://github.com/jaseg/python-mpv/archive/v${version}.tar.gz"
-checksum=fe14008723fd3c380098e87a0fec811fca6e8885dd9501e20ee1db29aa4920a0
+checksum=652a4c35829f1faaa308314d1297911fdfdcd33c77dfac32d47a6f4dd958f11d
next reply other threads:[~2024-04-28 11:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 11:52 kshade [this message]
2024-04-28 16:38 ` [PR PATCH] [Updated] " kshade
2024-04-28 16:40 ` kshade
2024-04-28 16:43 ` [PR PATCH] [Closed]: " kshade
2024-04-28 16:54 ` 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-50097@inbox.vuxu.org \
--to=kshade@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).