[Git-commits] [grml/grml-autoconfig] fc67c1: config_language: rely on console-setup for keyboar...

[Michael Prokop]

  Branch: refs/heads/master
  Home:   https://github.com/grml/grml-autoconfig
  Commit: fc67c1849a4eed7c2c0586dd65d77cec7d053768
      https://github.com/grml/grml-autoconfig/commit/fc67c1849a4eed7c2c0586dd65d77cec7d053768
  Author: Michael Prokop <mika at grml.org>
  Date:   2018-12-29 (Sat, 29 Dec 2018)

  Changed paths:
    M autoconfig.functions

  Log Message:
  -----------
  config_language: rely on console-setup for keyboard + font handling

Our old approach with running loadkeys, setting console font and
invoking unicode_start via grml-autoconfig is incomplete for nowadays'
environments.

We tried to fix that by changing the order in which we set up the fonts,
runnning loadkeys and finally invoking unicode_start (see commit
c820a66a69). But this changed only the behavior on tty1, the other
consoles still had problems when trying to display unicode characters
(see e.g. `systemctl status` output).

Instead when running under systemd rely on console-setup, by assuming
/etc/default/console-setup is set up as needed (implemented in grml-live
>=0.33.4) and adjusting /etc/default/keyboard according to
keyboard=.../lang=... boot options. Finally we invoke the console-setup
service.  (We might want to handle this outside of grml-autoconfig in
the future, but this approach for now guarantees to execute this in the
right order and not spit on the console at the end of the boot process).

Closes: grml/grml-autoconfig#9, grml/grml#50
Thanks: Darshaka Pathirana for debugging this


  Commit: 5ee88545febd109443645f5a4eb087dd5ae2c5f8
      https://github.com/grml/grml-autoconfig/commit/5ee88545febd109443645f5a4eb087dd5ae2c5f8
  Author: Michael Prokop <mika at grml.org>
  Date:   2018-12-29 (Sat, 29 Dec 2018)

  Changed paths:
    M debian/changelog

  Log Message:
  -----------
  Release new version 0.18.1


Compare: https://github.com/grml/grml-autoconfig/compare/8be7a425a159...5ee88545febd
      **NOTE:** This service has been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/

      Functionality will be removed from GitHub.com on January 31st, 2019.