Your message dated Tue, 09 Apr 2019 12:48:33 +0000
with message-id <[email protected]>
and subject line unblock kpmcore
has caused the Debian Bug report #926710,
regarding unblock: kpmcore/3.3.0-5
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
926710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926710
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: unblock

Please unblock package kpmcore

The recently uploaded cryptsetup defaults to luks2, which is not yet supported 
in grub.

kpmcore does not yet support choosing luks implementation, so this patch 
specifies
that luks1 should be used, maintaining its previous behaviour. kpmcore is used
by calamares to configure full-disk encryption. Without this patch, live media 
installed
using calamares and full disk encryption can't boot.

Debdiff:
"""
--- kpmcore-3.3.0/debian/changelog      2018-11-27 09:54:56.000000000 +0200
+++ kpmcore-3.3.0/debian/changelog      2019-04-06 12:40:05.000000000 +0200
@@ -1,3 +1,9 @@
+kpmcore (3.3.0-5) unstable; urgency=medium
+
+  * Use luks1 format only
+
+ -- Jonathan Carter <[email protected]>  Sat, 06 Apr 2019 12:40:05 +0200
+
 kpmcore (3.3.0-4) unstable; urgency=medium

     * Version bump (no changes)
     diff -Nru kpmcore-3.3.0/debian/patches/force-luks1 
kpmcore-3.3.0/debian/patches/force-luks1
     --- kpmcore-3.3.0/debian/patches/force-luks1       1970-01-01 
02:00:00.000000000 +0200
     +++ kpmcore-3.3.0/debian/patches/force-luks1       2019-04-06 
12:40:05.000000000 +0200
     @@ -0,0 +1,15 @@
     +Description: Force luks1 for new filesystems
     +
     +Force luks1 since cryptsetup 2.1 defaults to luks2 which isn't well 
supported.
     +Author: Jonathan Carter <[email protected]>
     +
     +--- kpmcore-3.3.0.orig/src/fs/luks.cpp
     ++++ kpmcore-3.3.0/src/fs/luks.cpp
     +@@ -125,6 +125,7 @@ bool luks::create(Report& report, const
     +                                 QStringLiteral("512"),
     +                                 QStringLiteral("--batch-mode"),
     +                                 QStringLiteral("--force-password"),
     ++                                QStringLiteral("--type=luks1"),
     +                                 QStringLiteral("luksFormat"),
     +                                 deviceNode });
     +     if (!( createCmd.start(-1) &&
     diff -Nru kpmcore-3.3.0/debian/patches/series 
kpmcore-3.3.0/debian/patches/series
     --- kpmcore-3.3.0/debian/patches/series    1970-01-01 02:00:00.000000000 
+0200
     +++ kpmcore-3.3.0/debian/patches/series    2019-04-06 12:40:05.000000000 
+0200
     @@ -0,0 +1 @@
     +force-luks1
"""

unblock kpmcore/3.3.0-5

--- End Message ---
--- Begin Message ---
Unblocked kpmcore.

--- End Message ---

Reply via email to