From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com
 [IPv6:2a00:1450:4864:20::332])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Tue,  5 Feb 2019 16:30:00 +0100 (CET)
Received: by mail-wm1-x332.google.com with SMTP id m22so4132303wml.3
 for <dm-crypt@saout.de>; Tue, 05 Feb 2019 07:29:59 -0800 (PST)
Received: from [192.168.2.28] (39.35.broadband4.iol.cz. [85.71.35.39])
 by smtp.gmail.com with ESMTPSA id e27sm27063019wra.67.2019.02.05.07.29.56
 for <dm-crypt@saout.de>
 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Tue, 05 Feb 2019 07:29:57 -0800 (PST)
References: <20180727081626.GA29834@localhost.localdomain>
 <d349eeb9-4509-e188-4bb2-90854bcc9a69@gmail.com>
 <20180730204718.GA16752@localhost.localdomain>
 <20180731060030.GA15852@h-174-65.A328.priv.bahnhof.se>
 <20180731075342.GA25101@localhost.localdomain>
 <aa607562-adad-6aaa-1865-df1e43eea44a@gmail.com>
 <20190125135442.GA24862@fripost.org>
 <71db2159-bb20-c9a5-19bc-c597b2a33788@gmail.com>
From: Milan Broz <gmazyland@gmail.com>
Message-ID: <6f275116-1ee1-6f4a-01ef-cbe1a5671820@gmail.com>
Date: Tue, 5 Feb 2019 16:29:55 +0100
MIME-Version: 1.0
In-Reply-To: <71db2159-bb20-c9a5-19bc-c597b2a33788@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Debian installer formatting LUKS2 devices by default?
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <https://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <https://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <https://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

On 25/01/2019 15:31, Milan Broz wrote:
> 
> - 2.1 should be released 5.2.2019
> 
> (Definitely not later, some slight change that it happens earlier.

And this always happens when an exact release date is announced,
unexpected problems appears :-)

So 2.1 will happen later this week, I see some strange failures with the recent
kernel we need to sort out.

Milan