From: zdykstra <zdykstra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] zfs: update to 2.1.4.
Date: Fri, 25 Mar 2022 16:20:39 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36333@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 809 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.4
https://github.com/void-linux/void-packages/pull/36333
zfs: update to 2.1.4.
#### Testing the changes
- I tested the changes in this PR: **YES**
-
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- x86_64-musl
ZFS 2.1.4 adds a fix for kernel 5.16 on [specific x86 CPUs](https://github.com/openzfs/zfs/issues/13210). I've booted my system with this package, but it could use wider real-world testing on Void systems.
A patch file from https://github.com/void-linux/void-packages/pull/36333.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-zfs-2.1.4-36333.patch --]
[-- Type: text/x-diff, Size: 1156 bytes --]
From e47c1ed90aa497a91379b25ded0eeeda2e578bd9 Mon Sep 17 00:00:00 2001
From: Zach Dykstra <dykstra.zachary@gmail.com>
Date: Fri, 25 Mar 2022 09:56:17 -0500
Subject: [PATCH] zfs: update to 2.1.4.
---
srcpkgs/zfs/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/zfs/template b/srcpkgs/zfs/template
index 477c39614cd0..6c7b69345fd3 100644
--- a/srcpkgs/zfs/template
+++ b/srcpkgs/zfs/template
@@ -1,6 +1,6 @@
# Template file for 'zfs'
pkgname=zfs
-version=2.1.3
+version=2.1.4
revision=1
build_style=gnu-configure
configure_args="--with-config=user --with-mounthelperdir=/usr/bin
@@ -15,7 +15,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=b61b644547793f409cafd6538a52d78f2f72b0cd013e88340882457c8c9b43fd
+checksum=3b52c0d493f806f638dca87dde809f53861cd318c1ebb0e60daeaa061cf1acf6
# dkms must be before initramfs-regenerate to build modules before images
triggers="dkms initramfs-regenerate"
dkms_modules="zfs ${version}"
next reply other threads:[~2022-03-25 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 15:20 zdykstra [this message]
2022-03-25 19:51 ` ahesford
2022-03-25 20:27 ` [PR PATCH] [Merged]: " Vaelatern
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-36333@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).