Github messages for voidlinux
 help / color / mirror / Atom feed
From: FollieHiyuki <FollieHiyuki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] mpDris2: update to 0.9.1
Date: Wed, 02 Jun 2021 00:24:30 +0200	[thread overview]
Message-ID: <20210601222430.MlWuFYvO47r_jhvy4kneqhLQo3x76Qa2SMDmL3e90tM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31250@inbox.vuxu.org>

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

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

https://github.com/FollieHiyuki/void-packages mpDris2-update
https://github.com/void-linux/void-packages/pull/31250

mpDris2: update to 0.9.1
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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/31250.patch is attached

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

From 92f93ff246e51d076330d1aaf8824b1d23e9e0f9 Mon Sep 17 00:00:00 2001
From: FollieHiyuki <folliekazetani@protonmail.com>
Date: Wed, 2 Jun 2021 01:06:18 +0300
Subject: [PATCH] mpDris2: update to 0.9.1

---
 srcpkgs/mpDris2/template | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/mpDris2/template b/srcpkgs/mpDris2/template
index bd2a266cd517..bb1cc605979d 100644
--- a/srcpkgs/mpDris2/template
+++ b/srcpkgs/mpDris2/template
@@ -1,16 +1,16 @@
 # Template file for 'mpDris2'
 pkgname=mpDris2
-version=0.8
+version=0.9.1
 revision=1
 build_style=gnu-configure
 hostmakedepends="autoconf automake intltool gettext-devel"
-depends="python3 python3-dbus python3-gobject python3-mpd2 python3-mutagen"
+depends="python3-dbus python3-gobject python3-mpd2 python3-mutagen"
 short_desc="Provides MPRIS 2 support to mpd (Music Player Daemon)"
 maintainer="Illia Shestakov <ishestakov@airmail.cc>"
 license="GPL-3.0-only"
 homepage="https://github.com/eonpatapon/mpDris2"
 distfiles="https://github.com/eonpatapon/mpDris2/archive/${version}.tar.gz"
-checksum=b6b15c1fdddf16a6d74485ad09f56ed353a317e149c37475c00a279186da4391
+checksum=d0f0467841e7866310cff44a1063334a9c776a64fd594815d926670b765fbee6
 
 pre_configure() {
 	NOCONFIGURE=1 ./autogen.sh
@@ -20,6 +20,5 @@ post_install() {
 	rm -f ${DESTDIR}/usr/lib/systemd/user/mpDris2.service
 	vsv mpDris2
 	vdoc README.md
-	vlicense COPYING
 	vsconf src/mpDris2.conf
 }

  reply	other threads:[~2021-06-01 22:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 22:06 [PR PATCH] " FollieHiyuki
2021-06-01 22:24 ` FollieHiyuki [this message]
2021-06-02  4:17 ` [PR PATCH] [Merged]: " ericonr

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=20210601222430.MlWuFYvO47r_jhvy4kneqhLQo3x76Qa2SMDmL3e90tM@z \
    --to=folliehiyuki@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).