From: raid5atemyhomework via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 49710@debbugs.gnu.org
Subject: bug#49710: [PATCH] gnu: Update OpenZFS to 2.1.0.
Date: Fri, 23 Jul 2021 15:07:05 +0000 [thread overview]
Message-ID: <hnWKPsStLroua0pG1kyYHqam2ADsbaqPr1T1e7RdChJWKmXGUgC4YrLFB-tjkZYQvgV2YmOYinqfi9UwUMbh-DkFWHwt5Nh53YdW1FvpRas=@protonmail.com> (raw)
From 14446422d6f7873b29d2fe04a9528de867b854b8 Mon Sep 17 00:00:00 2001
From: raid5atemyhomework <raid5atemyhomework@protonmail.com>
Date: Fri, 23 Jul 2021 23:01:30 +0800
Subject: [PATCH] gnu: Update OpenZFS to 2.1.0.
* gnu/packages/file-systems.scm [zfs]: Update to 2.1.0, add
support for new compatibility feature.
---
gnu/packages/file-systems.scm | 23 +++++++++++++++++++++--
1 file changed, 21 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/file-systems.scm b/gnu/packages/file-systems.scm
index b6d0bcbc55..463cc3a8b5 100644
--- a/gnu/packages/file-systems.scm
+++ b/gnu/packages/file-systems.scm
@@ -1171,7 +1171,7 @@ with the included @command{xfstests-check} helper.")
(define-public zfs
(package
(name "zfs")
- (version "2.0.5")
+ (version "2.1.0")
(outputs '("out" "module" "src"))
(source
(origin
@@ -1180,7 +1180,7 @@ with the included @command{xfstests-check} helper.")
"/download/zfs-" version
"/zfs-" version ".tar.gz"))
(sha256
- (base32 "1jbfm18hh9x4a9s5d7si8lapmq2aniphyriif9flrgsff26lj5rs"))))
+ (base32 "0kzkggwznp4m3503f2m4lcinbl99jg50j4asrwfpfk1862vdrgb0"))))
(build-system linux-module-build-system)
(arguments
`(;; The ZFS kernel module should not be downloaded since the license
@@ -1211,6 +1211,25 @@ with the included @command{xfstests-check} helper.")
(util-linux (assoc-ref inputs "util-linux"))
(nfs-utils (assoc-ref inputs "nfs-utils"))
(kmod (assoc-ref inputs "kmod-runtime")))
+ ;; New feature "compatibility=" in 2.1.0.
+ ;; This feature looks up in two locations:
+ ;; /etc/zfs/compatibility.d/
+ ;; /usr/share/zfs/compatibility.d/
+ ;; The first is intended for system-specific compatibility
+ ;; sets, while the second is what is installed with the
+ ;; OpenZFS package, so use the absolute path for the first
+ ;; (which requires patching in the file) and the store path
+ ;; for the second (which it gets by default).
+ (substitute* "include/sys/fs/zfs.h"
+ (("#define\tZPOOL_SYSCONF_COMPAT_D.*$")
+ ; Use absolute path.
+ "#define\tZPOOL_SYSCONF_COMPAT_D\t\"/etc/zfs/compatibility.d\"\n"))
+ ;; Also update the manual, which uses absolute paths, so that
+ ;; /usr/share/zfs/compatibility.d/ is referred via the store.
+ (substitute* '("man/man8/zpoolprops.8"
+ "man/man5/zpool-features.5")
+ (("/usr/share/zfs/compatibility.d")
+ (string-append out "/share/zfs/compatibility.d")))
(substitute* "etc/Makefile.in"
;; This just contains an example configuration file for
;; configuring ZFS on traditional init systems, skip it
--
2.31.1
next reply other threads:[~2021-07-23 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 15:07 raid5atemyhomework via Bug reports for GNU Guix [this message]
2021-07-23 16:54 ` bug#49710: [PATCH v2] gnu: Update OpenZFS to 2.1.0 raid5atemyhomework via Bug reports for GNU Guix
2021-08-01 9:41 ` raid5atemyhomework via Bug reports for GNU Guix
2021-08-02 16:00 ` Efraim Flashner
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='hnWKPsStLroua0pG1kyYHqam2ADsbaqPr1T1e7RdChJWKmXGUgC4YrLFB-tjkZYQvgV2YmOYinqfi9UwUMbh-DkFWHwt5Nh53YdW1FvpRas=@protonmail.com' \
--to=bug-guix@gnu.org \
--cc=49710@debbugs.gnu.org \
--cc=raid5atemyhomework@protonmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).