ubuntu-image should allow to disable console-conf at build time

[Oliver Grawert]

currently various odd hacks exist to make sure that console-conf does not start up on appliance or kiosk systems that are supposed to be user-less and get managed only via the snapd REST API.

to disable console-conf starting up the file /var/lib/console-conf/complete must exist in the system. to allow disabling console-conf at image build time (to overcome the various hacks) something like a --no-console-conf option should be added to ubuntu-image so no hacks are necessary anymore for this type of images.

[Łukasz Zemczak (sil2100)]

Prepared a PR for this here:
https://github.com/CanonicalLtd/ubuntu-image/pull/185

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-image - 1.10+20.10ubuntu1

---------------
ubuntu-image (1.10+20.10ubuntu1) groovy; urgency=medium

  [ Łukasz 'sil2100' Zemczak ]
  * Add a quick option to disable console-conf. (LP: #1866002)
  * Disable some of the unsupported features for UC20 models. (LP: #1875431)
    - --disable-console-conf
    - --cloud-init
    - Running the post-populate-rootfs hook.
  * Do not create an empty /boot on the system-seed partition.
  * Switch the approach of building UC20 images to ensure that all partitions
    defined in the gadget are considered in image size calculations.
    (LP: #1859973)

  [ Michael Hudson-Doyle ]
  * Add dependency on fdisk now that it is no longer Essential. (LP: #1877485)

  [ Maciej Borzecki ]
  * Do not overwrite the files that snap prepare-image has created.
    (LP: #1884247)

  [ Dimitri John Ledkov ]
  * Pacify flake8 in groovy.

 -- Łukasz 'sil2100' Zemczak <email address hidden> Thu, 03 Sep 2020 10:20:28 +0200