Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: "José Luis Salvador Rufo" <salvador.joseluis@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/zfs: bump version to 2.2.2
Date: Fri, 1 Dec 2023 11:32:58 +0100	[thread overview]
Message-ID: <20231201103258.GO3177259@scaer> (raw)
In-Reply-To: <20231201073304.1599298-2-salvador.joseluis@gmail.com>

José, All,

On 2023-12-01 08:33 +0100, José Luis Salvador Rufo spake thusly:
> This release contains an important fix for a data corruption
> bug. Full details are in the issue [1] and bug fix [2].
> 
> 1. https://github.com/openzfs/zfs/issues/15526
> 2. https://github.com/openzfs/zfs/pull/15571
> 
> Signed-off-by: José Luis Salvador Rufo <salvador.joseluis@gmail.com>

Since this is a data-corruption fix, I've applied to master, after
backporting the 2.2.0 bump from the next branch. Thanks!

Regards,
Yann E. MORIN.

> ---
>  package/zfs/zfs.hash | 4 ++--
>  package/zfs/zfs.mk   | 2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/package/zfs/zfs.hash b/package/zfs/zfs.hash
> index b02c49234a..01c86f2bd6 100644
> --- a/package/zfs/zfs.hash
> +++ b/package/zfs/zfs.hash
> @@ -1,5 +1,5 @@
> -# Locally computed
> -sha256  42035fd059faa25a09cd511b24a57b8ad1285cb69127f2a0043b98562c5ec690  zfs-2.2.0.tar.gz
> +# From https://github.com/openzfs/zfs/releases/download/zfs-2.2.2/zfs-2.2.2.sha256.asc
> +sha256  76bc0547d9ba31d4b0142e417aaaf9f969072c3cb3c1a5b10c8738f39ed12fc9  zfs-2.2.2.tar.gz
>  
>  # Hash for license files:
>  sha256  1ffb70c33c4f79f04e947facc5c7851f289609256aacb47fc115f700427d9520  LICENSE
> diff --git a/package/zfs/zfs.mk b/package/zfs/zfs.mk
> index d85956c98b..a2c7b5351d 100644
> --- a/package/zfs/zfs.mk
> +++ b/package/zfs/zfs.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -ZFS_VERSION = 2.2.0
> +ZFS_VERSION = 2.2.2
>  ZFS_SITE = https://github.com/openzfs/zfs/releases/download/zfs-$(ZFS_VERSION)
>  ZFS_SELINUX_MODULES = zfs
>  ZFS_LICENSE = CDDL
> -- 
> 2.43.0
> 

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-12-01 10:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01  7:33 [Buildroot] [PATCH] package/zfs: bump version to 2.2.2 José Luis Salvador Rufo
2023-12-01 10:32 ` Yann E. MORIN [this message]
2023-12-01 20:10   ` Peter Korsgaard

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=20231201103258.GO3177259@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=salvador.joseluis@gmail.com \
    --cc=thomas.petazzoni@bootlin.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox