From: ftrvxmtrx <ftrvxmtrx@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] bindfs: update to 1.16.1, adopt
Date: Sun, 26 Jun 2022 18:49:53 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37697@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
There is a new pull request by ftrvxmtrx against master on the void-packages repository
https://github.com/ftrvxmtrx/void-packages bindfs-1.16.1
https://github.com/void-linux/void-packages/pull/37697
bindfs: update to 1.16.1, adopt
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (aarch64-musl)
A patch file from https://github.com/void-linux/void-packages/pull/37697.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-bindfs-1.16.1-37697.patch --]
[-- Type: text/x-diff, Size: 1228 bytes --]
From a7278d05b2cd7a12daf13cf3d5cecf5a6663b2bb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Sigrid=20Solveig=20Hafl=C3=ADnud=C3=B3ttir?=
<sigrid@ftrv.se>
Date: Sun, 26 Jun 2022 18:48:22 +0200
Subject: [PATCH] bindfs: update to 1.16.1, adopt
---
srcpkgs/bindfs/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/bindfs/template b/srcpkgs/bindfs/template
index beb18d37dcc1..e810fd4335a2 100644
--- a/srcpkgs/bindfs/template
+++ b/srcpkgs/bindfs/template
@@ -1,16 +1,16 @@
# Template file for 'bindfs'
pkgname=bindfs
-version=1.16.0
+version=1.16.1
revision=1
build_style=gnu-configure
hostmakedepends="pkg-config"
makedepends="fuse3-devel"
short_desc="FUSE filesystem for mounting a directory to another location"
-maintainer="Orphaned <orphan@voidlinux.org>"
+maintainer="Sigrid Solveig Haflínudóttir <sigrid@ftrv.se>"
license="GPL-2.0-or-later"
homepage="https://bindfs.org"
changelog="https://bindfs.org/docs/ChangeLog.utf8.txt"
distfiles="https://bindfs.org/downloads/bindfs-${version}.tar.gz"
-checksum=02ebefaaa64e1b044fc5c743c5829aad21ed6f7145f4db0723bcc45f085781f6
+checksum=55ea3d2aa8e48d0bea23b7c0b03950cfeb492355bfd8dbb8a173a1e383f228bc
#cannot mount
make_check=no
next reply other threads:[~2022-06-26 16:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 16:49 ftrvxmtrx [this message]
2022-06-26 21:06 ` [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-37697@inbox.vuxu.org \
--to=ftrvxmtrx@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).