From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mathieu Othacehe <m.othacehe@gmail.com>
Subject: Re: 1.1.0rc2 available for testing!
Date: Mon, 13 Apr 2020 13:54:34 +0200
Message-ID: <87eesrmwhx.fsf@gmail.com>
References: <878sj1qcw7.fsf@gnu.org>
 <20200413074259.ombdnc7woox2armu@pelzflorian.localdomain>
 <87ftd7mzvs.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:34227)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <m.othacehe@gmail.com>) id 1jNxfi-0007CK-7b
 for guix-devel@gnu.org; Mon, 13 Apr 2020 07:54:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <m.othacehe@gmail.com>) id 1jNxfh-0006CU-D5
 for guix-devel@gnu.org; Mon, 13 Apr 2020 07:54:38 -0400
In-Reply-To: <87ftd7mzvs.fsf@gnu.org> ("Ludovic
 \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\=
 \=\?utf-8\?Q\?s\?\= message of "Mon, 13 Apr 2020 12:41:27 +0200")
List-Id: "Development of GNU Guix and the GNU System distribution."
 <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org
Sender: "Guix-devel"
 <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
To: Ludovic =?utf-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Cc: guix-devel@gnu.org, Keyhenge <key@keyhenge.xyz>


Hey,

> This bug is not about rc2, is it?  WDYT Mathieu?

No, I think its a Guile-Parted bug, I forget about, that causes
installer failures when the partition size is > 1 TiB. It has presumably
always been around.

I did a Guile-Parted 0.0.3 release and updated the package definition on
master. However, I don't have the hardware to test the fix. So maybe we
shouldn't block the 1.1.0 for this and wait for more feedback.

Mathieu