[Bug 1528861] Re: cryptsetup can not coexist with console-common

[Steve Langasek]

On Thu, Dec 24, 2015 at 09:20:31AM -0000, Steven Shiau wrote:
> Thanks.

> The reason we need to use install-keymap is it's easier to do that in
> unattended mode, i.e.  e.g.  to set the French keyboard, just use:
> install-keymap /usr/share/keymaps/i386/azerty/fr-latin9.kmap.gz

> So if console-common is obsolete, is that possible to use console-setup
> and keyboard-configuration to configure the keymap in unattended,
> non-interactive way?  If so, that would be great.  Appreciate.

For an image that accepts debconf preseeding at installation time, you can
do so with the following settings:

  keyboard-configuration/layoutcode fr
  keyboard-configuration/variantcode oss_latin9

There are various ways that this information can be fed into a live image
that doesn't use debconf for the keyboard configuration.  For instance,
ubuntu-default-builder supports configuring the default keyboard for the
live image using i18n/keyboard.txt with a single line of 'fr oss_latin9'.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/1528861

Title:
  cryptsetup can not coexist with console-common

Status in cryptsetup package in Ubuntu:
  New

Bug description:
  The package cryptsetup can not coexist with console-common due to
  cryptsetup depends on plymouth. However, plymouth conflicts with
  console-common, so this makes the cryptsetup can not coexist with
  console-common. This does not happen on Debian Sid because cryptsetup
  on Debian does not depend on plymouth. We need console-common is
  because we need the program install-keymap from console-common for the
  live CD we want to create.

  # cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.04
  DISTRIB_CODENAME=xenial
  DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)"

  # apt-get install cryptsetup console-common
  Reading package lists... Done
  Building dependency tree       
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   cryptsetup : Depends: plymouth but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  Thanks.

  Steven.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1528861/+subscriptions