all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: antlers via Guix-patches via <guix-patches@gnu.org>
To: 67311@debbugs.gnu.org
Cc: antlers <antlers@illucid.net>,
	efraim@flashner.co.il, mail@cbaines.net, mail@nicolasgoaziou.fr,
	kaelyn.alexi@protonmail.com
Subject: [bug#67311] [PATCH v2] gnu: zfs: Update to 2.1.14.
Date: Tue,  5 Dec 2023 20:02:54 +0000	[thread overview]
Message-ID: <ba02c88f8e3a4b5a39ed010680b48b7add81f455.1701806574.git.antlers@illucid.net> (raw)
In-Reply-To: <41c282cbabafb64b783fcbdf8ffbf2bf213185af.1700511902.git.kaelyn.alexi@protonmail.com>

* gnu/packages/file-systems.scm (zfs): Update to 2.1.14.

Change-Id: I696467868924f1135ba678e8e743955d3767618f
---

This week's update contains the backported fix for the recent file-system
corruption bug.

I thought I had an issue because it doesn't build against linux-libre, but that
was true of the version 2.1.12 as well; I presume the status-quo is that anyone
using this package should define a variant against their current kernel by
setting the #:linux build-system argument, and can confirm that this patch
builds against linux-libre-lts as of GNU Guix 6ab6c02a.

Thanks to everyone who's been helping keep this up to date!

 gnu/packages/file-systems.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/file-systems.scm b/gnu/packages/file-systems.scm
index bc061a5958..05074b2eb4 100644
--- a/gnu/packages/file-systems.scm
+++ b/gnu/packages/file-systems.scm
@@ -1365,7 +1365,7 @@ (define-public xfstests
 (define-public zfs
   (package
     (name "zfs")
-    (version "2.1.12")
+    (version "2.1.14")
     (outputs '("out" "module" "src"))
     (source
       (origin
@@ -1374,7 +1374,7 @@ (define-public zfs
                               "/download/zfs-" version
                               "/zfs-" version ".tar.gz"))
           (sha256
-           (base32 "0vbf9kfryprb2mbb65jllf6xpsy44xskshglyqqwj4iyxmma5nk4"))))
+           (base32 "0gzansmin40llxxh2zkgpdyp41ikd8s5hv5mpwhpcivk1q8fv7sh"))))
     (build-system linux-module-build-system)
     (arguments
      (list

base-commit: 6ab6c02affbfe921241fe07e7554b5a0ab39587e
-- 
2.41.0





  reply	other threads:[~2023-12-05 20:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20 20:25 [bug#67311] [PATCH] gnu: zfs: Update to 2.1.13 Kaelyn Takata via Guix-patches via
2023-12-05 20:02 ` antlers via Guix-patches via [this message]
2023-12-18 19:11   ` bug#67311: [PATCH v2] gnu: zfs: Update to 2.1.14 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ba02c88f8e3a4b5a39ed010680b48b7add81f455.1701806574.git.antlers@illucid.net \
    --to=guix-patches@gnu.org \
    --cc=67311@debbugs.gnu.org \
    --cc=antlers@illucid.net \
    --cc=efraim@flashner.co.il \
    --cc=kaelyn.alexi@protonmail.com \
    --cc=mail@cbaines.net \
    --cc=mail@nicolasgoaziou.fr \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.