unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: raid5atemyhomework via Guix-patches via <guix-patches@gnu.org>
To: 46454@debbugs.gnu.org
Subject: [bug#46454] [PATCH] gnu: Update zfs.
Date: Fri, 12 Feb 2021 02:23:23 +0000	[thread overview]
Message-ID: <TjDF-9t9w3P5lOPGXn4yxmF2mAWG7JqPd_RMNtsMB4Ydy_x3fy6IvmEu8-OL74PNEifrvRuIAsnaWVbt6g_36Mt3r7myiuI2aauXEL6hIoM=@protonmail.com> (raw)

Please prioritize, as this release fixes a (minor and low-probability) security issue: https://github.com/openzfs/zfs/issues/11474#issuecomment-775383738 Upstream even released this point release "early" in order to get this fix deployed, we should do same over in Guix.

Minimally tested with `guix build zfs`.  Given that the difference from 2.0.2 is very tiny (the only substantive change is the fix to the above issue, this point release only exists to fix that one issue), I expect no particular problems updating in Guix.



From 753ecc32252b8b7d3e806ed7a16b2771c6b78559 Mon Sep 17 00:00:00 2001
From: raid5atemyhomework <raid5atemyhomework@protonmail.com>
Date: Fri, 12 Feb 2021 10:09:56 +0800
Subject: [PATCH] gnu: Update zfs.

* gnu/packages/file-systems.scm (zfs): Update to 2.0.3.
---
 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 b7321addd4..118e0d9faf 100644
--- a/gnu/packages/file-systems.scm
+++ b/gnu/packages/file-systems.scm
@@ -847,7 +847,7 @@ APFS.")
 (define-public zfs
   (package
     (name "zfs")
-    (version "2.0.2")
+    (version "2.0.3")
     (outputs '("out" "module" "src"))
     (source
       (origin
@@ -856,7 +856,7 @@ APFS.")
                               "/download/zfs-" version
                               "/zfs-" version ".tar.gz"))
           (sha256
-           (base32 "090b2pp0cgzkjcnbjf8ms28dah5dff8s04q31z62czapwiy0drdx"))))
+           (base32 "0fg5hz1yy2z5ah0hzjv3xy5vcg1c214rps90dr80lfkalx5gd506"))))
     (build-system linux-module-build-system)
     (arguments
      `(;; The ZFS kernel module should not be downloaded since the license
--
2.30.0





             reply	other threads:[~2021-02-12  2:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12  2:23 raid5atemyhomework via Guix-patches via [this message]
2021-02-12  5:57 ` bug#46454: [PATCH] gnu: Update zfs 宋文武
2021-02-13 15:00 ` [bug#46454] " Tobias Geerinckx-Rice via Guix-patches via
2021-02-13 16:18   ` Tobias Geerinckx-Rice via Guix-patches via

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='TjDF-9t9w3P5lOPGXn4yxmF2mAWG7JqPd_RMNtsMB4Ydy_x3fy6IvmEu8-OL74PNEifrvRuIAsnaWVbt6g_36Mt3r7myiuI2aauXEL6hIoM=@protonmail.com' \
    --to=guix-patches@gnu.org \
    --cc=46454@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).