[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#930330: marked as done (unblock: cryptsetup/2.1.0-5)

Your message dated Sat, 15 Jun 2019 11:21:39 +0000
with message-id <E1hc6kd-00041t-4m@respighi.debian.org>
and subject line unblock cryptsetup
has caused the Debian Bug report #930330,
regarding unblock: cryptsetup/2.1.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 owner@bugs.debian.org
immediately.)


-- 
930330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930330
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
Tags: d-i

Hi there,

During a chat last at MiniDebConf Hamburg last week-end we (cryptsetup
package maintainers + KiBi + ivodd) discussed a path forward for #927165
(debian-installer: improve support for LUKS) in Buster.

In the cryptsetup side of thing, we produced an online document/guide/notes
on GRUB unlocking for both LUKS devices, including extra work-arounds for
LUKS2: https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html

The document isn't shipped to any of cryptsetup/2.1.0-5's binary packages,
because it'll likely be amended in later d-i Buster RCs (based on which
flag/workaround is implemented there), and shipping the document to our
binary packages would then require extra roundtrips and unblock requests.

Instead, we added a section "Unlocking LUKS devices from GRUB" to
README.Debian with a link to the aforementioned document [0].

The debdiff diffstat (without ‘--ignore-space’) between 2:2.1.0-4 and
2:2.1.0-5 goes as follows:

 README.Debian                |  196 ++++++++++++-----------
 README.debug                 |   71 ++++++++
 README.gnupg                 |   34 ++--
 README.gnupg-sc              |   36 ++--
 README.initramfs             |  148 ++++++++++--------
 README.keyctl                |   51 +++---
 README.opensc                |   99 +++++-------
 README.source                |    2 
 changelog                    |   12 +
 cryptsetup-run.docs          |    1 
 doc/pandoc/encrypted-boot.md |  353 +++++++++++++++++++++++++++++++++++++++++++
 doc/pandoc/index.md          |   24 ++
 doc/pandoc/pandoc.css        |   74 +++++++++
 gitlab-ci.yml                |   53 ++++++
 14 files changed, 894 insertions(+), 260 deletions(-)

There is a bit of clutter in the above:

  - New files gitlab-ci.yml and doc/pandoc/* are what let us build the
    docs for pages.debian.net.  These files are not shipped in any
    binary package.
  - Some minor cosmetic changes in README.* to comply with (Pandoc's)
    Mardown format.

Debdiff between 2:2.1.0-4 and 2:2.1.0-5 (with ‘--ignore-space’)
attached.  Again, the important bit for this unblock request is the new
section in README.Debian.  The remaining bits are documentation-only
changes.

unblock cryptsetup/2.1.0-5
Thanks for considering its inclusion in Buster!
Cheers,
-- 
Guilhem.

[0] The new section in README.Debian can also be found online at
    https://cryptsetup-team.pages.debian.net/cryptsetup/README.Debian.html#unlocking-luks-devices-from-grub

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Unblocked cryptsetup.

--- End Message ---
Reply to: