Github messages for voidlinux
 help / color / mirror / Atom feed
From: pfpulux <pfpulux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] mergerfs: update to 2.34.1.
Date: Sun, 22 Jan 2023 06:51:48 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41793@inbox.vuxu.org> (raw)

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

There is a new 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/41793

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

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

From a6c10104d3da701348b189ac603f8d373c7540d2 Mon Sep 17 00:00:00 2001
From: Pulux <pulux@pf4sh.eu>
Date: Sun, 22 Jan 2023 06:50:01 +0100
Subject: [PATCH] mergerfs: update to 2.34.1.

---
 srcpkgs/mergerfs/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/mergerfs/template b/srcpkgs/mergerfs/template
index eaa0c4e9bee2..7fe8662d3816 100644
--- a/srcpkgs/mergerfs/template
+++ b/srcpkgs/mergerfs/template
@@ -1,6 +1,6 @@
 # Template file for 'mergerfs'
 pkgname=mergerfs
-version=2.33.5
+version=2.34.1
 revision=1
 build_style=gnu-makefile
 make_use_env=yes
@@ -11,7 +11,7 @@ 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=dcfbc3faf241567fdf4da0ffd87a89833db18ddd176f20962f05751552780e54
+checksum=57e09ed53dc2cd591d7e6a0b291588ba0917ccaddd1226371c99630dc7de795c
 
 pre_build() {
 	# we build from source, spoof release tarball

             reply	other threads:[~2023-01-22  5:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22  5:51 pfpulux [this message]
2023-04-23  1:59 ` github-actions
2023-05-08  1:53 ` [PR PATCH] [Closed]: " github-actions

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-41793@inbox.vuxu.org \
    --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).