From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] fuse3: update to 3.11.0.
Date: Fri, 29 Jul 2022 09:43:18 +0200 [thread overview]
Message-ID: <20220729074318.nXtBxihO_Egk9Xx49QkReNTX9et9mXkBjfgsrvvACQA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38220@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
There is an updated pull request by motorto against master on the void-packages repository
https://github.com/motorto/void-packages fuse3-3.11.0
https://github.com/void-linux/void-packages/pull/38220
fuse3: update to 3.11.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-{musl,glibc}
A patch file from https://github.com/void-linux/void-packages/pull/38220.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fuse3-3.11.0-38220.patch --]
[-- Type: text/x-diff, Size: 1227 bytes --]
From 7da8c53aa90eb264594e424d58c8bf95e7b59554 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Cerqueira?= <acerqueira021@gmail.com>
Date: Sat, 23 Jul 2022 21:15:11 +0100
Subject: [PATCH] fuse3: update to 3.11.0.
---
srcpkgs/fuse3/template | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/fuse3/template b/srcpkgs/fuse3/template
index d71c58865fbe..405efe00a5a8 100644
--- a/srcpkgs/fuse3/template
+++ b/srcpkgs/fuse3/template
@@ -1,6 +1,6 @@
# Template file for 'fuse3'
pkgname=fuse3
-version=3.10.5
+version=3.11.0
revision=1
wrksrc="fuse-${version}"
build_style=meson
@@ -11,8 +11,9 @@ short_desc="Filesystem in Userspace 3.x"
maintainer="Anthony Iliopoulos <ailiop@altatus.com>"
license="GPL-2.0-or-later, LGPL-2.1-or-later"
homepage="https://github.com/libfuse/libfuse"
+changelog="https://raw.githubusercontent.com/libfuse/libfuse/master/ChangeLog.rst"
distfiles="https://github.com/libfuse/libfuse/releases/download/fuse-${version}/fuse-${version}.tar.xz"
-checksum=b2e283485d47404ac896dd0bb7f7ba81e1470838e677e45f659804c3a3b69666
+checksum=8982c4c521daf3974dda8a5d55d575c988da13a571970f00aea149eb54fdf14c
conf_files="/etc/fuse.conf"
# Tests require root
make_check=no
next prev parent reply other threads:[~2022-07-29 7:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 20:17 [PR PATCH] " motorto
2022-07-29 7:37 ` [PR REVIEW] " classabbyamp
2022-07-29 7:43 ` motorto [this message]
2022-07-29 7:43 ` motorto
2022-07-29 7:50 ` [PR PATCH] [Updated] " motorto
2022-07-29 8:23 ` [PR PATCH] [Merged]: " classabbyamp
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=20220729074318.nXtBxihO_Egk9Xx49QkReNTX9et9mXkBjfgsrvvACQA@z \
--to=motorto@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).