If a user requested the --sshcopyid option then it's supposed
to be run successfully, otherwise it might leave an inaccessible
system, so exit with error if execution of `ssh-add -L` fails.

While at it:

* simplify code (no need for $RC)
* don't fail if directory /root/.ssh exists already
* append keys to possibly existing /root/.ssh/authorized_keys
  file, instead of overwriting it

Use locally available public keys to authorise root login on the target
system.

Similar to ssh-copy-id(1) (without the -i option) it checks if `ssh-add
-L` provides any output, and if so those keys are appended to
`/root/.ssh/authorized_keys`.

Closes: grml/grml-debootstrap#128

Predictable Network Interface Names were missing the default
/etc/network/interfaces file when using the --defaultinterfaces option.

Added a Networking-Section in the man page to clarify how the network is
configured in the target system and fixed the documentation for the
options --vmfile and --vm. Both options automatically enable the
--defaultinterface option and not the --nointerfaces option.

Closes: grml/grml-debootstrap#126

Closes: https://github.com/grml/grml-debootstrap/pull/122
Thanks: Patrick Schleizer

There's no reason to say "use /dev/sda1 as system partition"
all the time, when we already mention that we "Install Debian on /dev/sda1".

Provide usage examples for mmdebstrap and LVM devices.

The --iso option also accepts mountpoint without any file: syntax,
which is more human-friendly.

Spotted by lintian (see tag override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS)

The --mntpoint option is quite unimportant, whereas --grub, --password
and --bootappend all require an argument. Instead the --hostname is
quite important. Adjust accordingly.

Add related debian/post* scripts for proper dpkg-maintscript-helper
rm_conffile support.

Since Zsh version v4.3.12-1 in Debian completions should
go to /usr/share/zsh/vendor-completions and are supported
there out-of-the-box.

The only known incompatibility so far is the --iso ... option.
Therefore abort grml-debootstrap if DEBOOTSTRAP=mmdebstrap
and --iso ... option are used at the same time.

Closes: https://github.com/grml/grml-debootstrap/issues/120

Installation takes ages with lvm 2.03.02-1 if /run/udev isn't
available in the target system, causing messages like:

| WARNING: Device /dev/[...] not initialized in udev database even after waiting 10000000 microseconds.

Especially when grub package gets installed (which invokes
vgs and related tools) this takes forever and looks like a
failing installation.

This /run/udev bind-mount is a workaround required for Debian/buster's
lvm2, at least until #918590 is resolved.

No further changes needed

The "bullseye" release doesn't exist on the Debian repositories
as such yet, though it's supposed to appear at least once buster
(AKA Debian v10.0) is stable.

On 2019-02-12 there's the soft-freeze starting for the Buster release.
Accordingly default to buster as new default within grml-debootstrap.

Closes: grml/grml-debootstrap#117

In September 2018 the backports service was migrated from backports.org
to an official service within the Debian project and repositories (see
https://www.debian.org/News/2010/20100905).

This means http://backports.debian.org/debian-backports no longer exists
as such. Accordingly update the URL to point to the Debian repositories
(using ${RELEASE}-backports).

VirtualBox 5.2.22 is available in current stretch-backports, testing
(buster) and unstable. The URL for VBoxGuestAdditions_5.2.1-118918.iso
no longer works (results in 404).

grml-debootstrap used to happily create a target directory in /dev if
for instance one forgot to partition sda. To avoid such a mistake it
feels better to abort the installation.

Closes: grml/grml-debootstrap#99

Fix typo in comment, while at it

With the integration of cmdlinesopts.clp into the main script
this directory is no longer relevant.

kpartx (sometimes) does not cleanup the loop devices when deleting the
partition devmappings. This is a known bug, see Debian Bug #891077.

This is change is a possible workaround for that issue.

Now aborting grml-debootstrap is possible without leaving unneded loop
devices behind.

split finalize_vm into grub_install and umount_target