Github messages for voidlinux
 help / color / mirror / Atom feed
From: pfpulux <pfpulux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] mergerfs: update to 2.33.5.
Date: Tue, 25 Oct 2022 06:55:13 +0200	[thread overview]
Message-ID: <20221025045513.dGBgyR5QL0UMH4ldnuaLw5nrIfMgW5ZZdOwM-W4rVJQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39841@inbox.vuxu.org>

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

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

https://github.com/pfpulux/void-packages mergerfs
https://github.com/void-linux/void-packages/pull/39841

mergerfs: update to 2.33.5.
<!-- 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 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/39841.patch is attached

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

From 6e3b199738629bb887e829075f9e2dea97a26ad3 Mon Sep 17 00:00:00 2001
From: Pulux <pulux@pf4sh.eu>
Date: Sun, 9 Oct 2022 18:43:57 +0200
Subject: [PATCH] mergerfs: update to 2.33.5.

---
 srcpkgs/mergerfs/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/mergerfs/template b/srcpkgs/mergerfs/template
index 1d5b8c6049be..badfa3ebf117 100644
--- a/srcpkgs/mergerfs/template
+++ b/srcpkgs/mergerfs/template
@@ -1,6 +1,6 @@
 # Template file for 'mergerfs'
 pkgname=mergerfs
-version=2.32.5
+version=2.33.5
 revision=1
 build_style=gnu-makefile
 make_use_env=yes
@@ -10,8 +10,8 @@ short_desc="FUSE union filesystem"
 maintainer="Orphaned <orphan@voidlinux.org>"
 license="ISC"
 homepage="https://github.com/trapexit/mergerfs"
-distfiles="${homepage}/archive/${version}.tar.gz"
-checksum=ddf86e4a05d834d173b78a617112b0b4cf3b65447da69f0474815558d5815340
+distfiles="https://github.com/trapexit/mergerfs/releases/download/${version}/mergerfs-${version}.tar.gz"
+checksum=dcfbc3faf241567fdf4da0ffd87a89833db18ddd176f20962f05751552780e54
 
 pre_build() {
 	# we build from source, spoof release tarball

  parent reply	other threads:[~2022-10-25  4:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-09 16:46 [PR PATCH] " pfpulux
2022-10-11  4:45 ` [PR REVIEW] " classabbyamp
2022-10-25  4:55 ` pfpulux [this message]
2022-10-25  5:03 ` [PR PATCH] [Updated] " pfpulux
2022-10-25  5:04 ` [PR PATCH] [Closed]: " pfpulux

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=20221025045513.dGBgyR5QL0UMH4ldnuaLw5nrIfMgW5ZZdOwM-W4rVJQ@z \
    --to=pfpulux@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).