From: zdykstra <zdykstra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] fuse-mp3fs: update to 1.1.1.
Date: Sun, 28 Mar 2021 21:18:20 +0200 [thread overview]
Message-ID: <20210328191820.nCqUmQ1o-XjFeW8sOCKe7d1I_u-MrYDuvLr2GtXqzE4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29814@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1606 bytes --]
There is an updated pull request by zdykstra against master on the void-packages repository
https://github.com/zdykstra/void-packages fuse-mp3fs-1.1.1
https://github.com/void-linux/void-packages/pull/29814
fuse-mp3fs: update to 1.1.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/29814.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fuse-mp3fs-1.1.1-29814.patch --]
[-- Type: text/x-diff, Size: 1114 bytes --]
From cadc74795fc1e72dcba9aacb7e6e6b99eea50f72 Mon Sep 17 00:00:00 2001
From: Zach Dykstra <dykstra.zachary@gmail.com>
Date: Sun, 28 Mar 2021 11:28:16 -0500
Subject: [PATCH] fuse-mp3fs: update to 1.1.1.
---
srcpkgs/fuse-mp3fs/template | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/fuse-mp3fs/template b/srcpkgs/fuse-mp3fs/template
index 09d11682cd84..8d0db5696651 100644
--- a/srcpkgs/fuse-mp3fs/template
+++ b/srcpkgs/fuse-mp3fs/template
@@ -1,6 +1,6 @@
# Template file for 'fuse-mp3fs'
pkgname=fuse-mp3fs
-version=1.0
+version=1.1.1
revision=1
wrksrc="mp3fs-${version}"
build_style=gnu-configure
@@ -11,4 +11,9 @@ maintainer="Zach Dykstra <dykstra.zachary@gmail.com>"
license="GPL-3.0-or-later"
homepage="https://khenriks.github.io/mp3fs/"
distfiles="https://github.com/khenriks/mp3fs/releases/download/v${version}/mp3fs-${version}.tar.gz"
-checksum=cbb52062d712e8dfd3491d0b105e2e05715d493a0fd14b53a23919694a348069
+checksum=942b588fb623ea58ce8cac8844e6ff2829ad4bc9b4c163bba58e3fa9ebc15608
+
+do_check() {
+ # The checks all need mount/unmount capabilities
+ :
+}
next prev parent reply other threads:[~2021-03-28 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 16:29 [PR PATCH] " zdykstra
2021-03-28 16:47 ` zdykstra
2021-03-28 19:14 ` Piraty
2021-03-28 19:15 ` Piraty
2021-03-28 19:18 ` zdykstra [this message]
2021-03-28 19:56 ` ericonr
2021-03-28 20:02 ` [PR PATCH] [Updated] " zdykstra
2021-03-28 20:03 ` zdykstra
2021-03-28 20:03 ` zdykstra
2021-03-29 12:26 ` [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=20210328191820.nCqUmQ1o-XjFeW8sOCKe7d1I_u-MrYDuvLr2GtXqzE4@z \
--to=zdykstra@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).