From: zdykstra <zdykstra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] zfs: update to 2.1.12.
Date: Wed, 07 Jun 2023 15:53:22 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44305@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
There is a new pull request by zdykstra against master on the void-packages repository
https://github.com/zdykstra/void-packages zfs-2.1.12
https://github.com/void-linux/void-packages/pull/44305
zfs: update to 2.1.12.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **NO**
This is largely a place-holder PR. Upstream has recently been issuing point releases 1 to 5 days after a release, so I'm opening this just to put the brakes on merging anything on our side. In ~7 days this can be considered viable to receive further testing and a merge if upstream bug reports look good.
CC'ing @Vaelatern
A patch file from https://github.com/void-linux/void-packages/pull/44305.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-zfs-2.1.12-44305.patch --]
[-- Type: text/x-diff, Size: 1158 bytes --]
From a242271d5e22073d7e2fde877ee1efc750ddb3be Mon Sep 17 00:00:00 2001
From: Zach Dykstra <dykstra.zachary@gmail.com>
Date: Wed, 7 Jun 2023 08:50:17 -0500
Subject: [PATCH] zfs: update to 2.1.12.
---
srcpkgs/zfs/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/zfs/template b/srcpkgs/zfs/template
index 914114f1cfb7..e53f25d27084 100644
--- a/srcpkgs/zfs/template
+++ b/srcpkgs/zfs/template
@@ -1,6 +1,6 @@
# Template file for 'zfs'
pkgname=zfs
-version=2.1.11
+version=2.1.12
revision=1
build_style=gnu-configure
configure_args="--with-config=user --with-mounthelperdir=/usr/bin
@@ -16,7 +16,7 @@ maintainer="Toyam Cox <Vaelatern@voidlinux.org>"
license="CDDL-1.0"
homepage="https://openzfs.github.io/openzfs-docs/"
distfiles="https://github.com/openzfs/zfs/releases/download/zfs-${version}/zfs-${version}.tar.gz"
-checksum=a54fe4e854d0a207584f1799a80e165eae66bc30dc8e8c96a1f99ed9d4d8ceb2
+checksum=64daa26aed3e12c931f6f4413d7527c4ebdb8da35416b356152b5f9fdd4c6e6d
# dkms must be before initramfs-regenerate to build modules before images
triggers="dkms initramfs-regenerate"
dkms_modules="zfs ${version}"
next reply other threads:[~2023-06-07 13:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 13:53 zdykstra [this message]
2023-06-07 15:11 ` [NOMERGE] " absrd
2023-06-12 10:34 ` absrd
2023-06-12 19:41 ` [PR PATCH] [Updated] " zdykstra
2023-06-13 15:38 ` zdykstra
2023-06-13 23:27 ` [PR PATCH] [Merged]: " Vaelatern
2023-06-07 15:09 [PR PATCH] " absrd
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-44305@inbox.vuxu.org \
--to=zdykstra@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).