From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: mpv-mpris: update to 0.6
Date: Fri, 24 Jun 2022 21:24:09 +0200 [thread overview]
Message-ID: <20220624192409.p0RfAFvVnsiLEM6JfxH8-SVjtrG9dsFsFXilj7Y5bnE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35592@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
There's a closed pull request on the void-packages repository
mpv-mpris: update to 0.6
https://github.com/void-linux/void-packages/pull/35592
Description:
<!-- 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 [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](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, aarch64-glibc
I also updated the install directory to `etc/mpv/scripts` as stated in the [package homepage](673aff031e7cc741edea68d7b4b0103d7b031d4a55755abb9e1be5dd4ec4e969) is where mpv actually looks for scripts. It was not being located properly in `/usr/lib/mpv-mpris`.
prev parent reply other threads:[~2022-06-24 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 19:03 [PR PATCH] " corbmr
2022-02-13 19:46 ` Duncaen
2022-02-14 0:43 ` corbmr
2022-02-20 11:12 ` paper42
2022-06-24 2:16 ` github-actions
2022-06-24 19:24 ` paper42 [this message]
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=20220624192409.p0RfAFvVnsiLEM6JfxH8-SVjtrG9dsFsFXilj7Y5bnE@z \
--to=paper42@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).