Christian PERRIER bubu...@debian.org (27/12/2012):
As far as I understand, the only risk you're taking here is triggering
the u-i update in situations where it wasn't exactly needed. Inshort,
a useless (but harmless) call.
That seems fair.
Thanks, uploaded.
Mraw,
KiBi.
signature.asc
Control: severity -1 important
Cyril Brulebois k...@debian.org (24/11/2012):
even though wheezy beta 4 images got built against a fixed
cryptsetup, the first boot-up with an encrypted LVM might lead to
the needed for typing the passphrase in qwerty.
I guess it might depend on what
Processing control commands:
severity -1 important
Bug #694156 [debian-installer] debian-installer: Wrong keymap at first boot-up
with encrypted LVM
Severity set to 'important' from 'normal'
--
694156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694156
Debian Bug Tracking System
Contact
Control: reassign -1 finish-install 2.40
Control: tag -1 patch pending
Cyril Brulebois k...@debian.org (26/12/2012):
Some ways to go forward:
1. patch console-setup's postinst to detect when cryptsetup is
installed, to kick an update-initramfs run.
This is going to be tracked in #696773;
Processing control commands:
reassign -1 finish-install 2.40
Bug #694156 [debian-installer] debian-installer: Wrong keymap at first boot-up
with encrypted LVM
Bug reassigned from package 'debian-installer' to 'finish-install'.
No longer marked as found in versions debian-installer/20121114.
Quoting Cyril Brulebois (k...@debian.org):
2. patch some d-i component to manually trigger an initramfs update
when cryptsetup and console-setup are installed; maybe some
finish-install thing?
As far as I understand, the only risk you're taking here is triggering
the u-i update
Package: debian-installer
Version: 20121114
Severity: normal
Tags: d-i
Hi,
even though wheezy beta 4 images got built against a fixed cryptsetup,
the first boot-up with an encrypted LVM might lead to the needed for
typing the passphrase in qwerty.
I guess it might depend on what components are
7 matches
Mail list logo
