From: m3tav3rse <m3tav3rse@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] mergerfs: update to 2.38.0.
Date: Thu, 07 Dec 2023 19:36:18 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47646@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
There is a new pull request by m3tav3rse against master on the void-packages repository
https://github.com/m3tav3rse/void-packages mergerfs
https://github.com/void-linux/void-packages/pull/47646
mergerfs: update to 2.38.0.
<!-- 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 [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
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 these architectures (if supported. mark crossbuilds):
- x86_64-glibc
- x86_64-musl (cross)
A patch file from https://github.com/void-linux/void-packages/pull/47646.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-mergerfs-47646.patch --]
[-- Type: text/x-diff, Size: 1282 bytes --]
From d71974b32c70e976cc707ee1eb30548ed60dfcb3 Mon Sep 17 00:00:00 2001
From: mtvrs <mtvrs@tuta.io>
Date: Thu, 7 Dec 2023 19:05:26 +0100
Subject: [PATCH] mergerfs: update to 2.38.0.
---
srcpkgs/mergerfs/template | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/mergerfs/template b/srcpkgs/mergerfs/template
index 7fe8662d38167..1ef0fa64776fa 100644
--- a/srcpkgs/mergerfs/template
+++ b/srcpkgs/mergerfs/template
@@ -1,6 +1,6 @@
# Template file for 'mergerfs'
pkgname=mergerfs
-version=2.34.1
+version=2.38.0
revision=1
build_style=gnu-makefile
make_use_env=yes
@@ -10,12 +10,11 @@ short_desc="FUSE union filesystem"
maintainer="Pulux <pulux@pf4sh.eu>"
license="ISC"
homepage="https://github.com/trapexit/mergerfs"
-distfiles="https://github.com/trapexit/mergerfs/releases/download/${version}/mergerfs-${version}.tar.gz"
-checksum=57e09ed53dc2cd591d7e6a0b291588ba0917ccaddd1226371c99630dc7de795c
+distfiles="https://github.com/trapexit/mergerfs/archive/refs/tags/${version}.tar.gz"
+checksum=cdb855c797da16ae668a2f71f76830151c377b38dee698c63db092ca1635d95e
pre_build() {
- # we build from source, spoof release tarball
- vsed -i "s|^VERSION=.*|VERSION=$pkgver|" tools/update-version
+ echo "$version" > VERSION
}
post_install() {
next reply other threads:[~2023-12-07 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 18:36 m3tav3rse [this message]
2023-12-22 21:05 ` [PR PATCH] [Merged]: " Duncaen
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-47646@inbox.vuxu.org \
--to=m3tav3rse@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).