Bug#926710: unblock: kpmcore/3.3.0-5
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
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 <jcc@debian.org> 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 <jcc@debian.org>
+
+--- 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
Reply to: