debian element no longer could build wheezy

[George Shuklin]

Commit a0f747932d0ef321355f62205d2e47b93ddc06dd made changes into debian-minimal element which broke Wheezy build process. Debian Wheezy uses sysv and attempt to install systemd-sysv cause it removal. As sysv is essential package it breaks build process:

Now build fails with following message:

The following packages will be REMOVED:
  sysvinit
The following NEW packages will be installed:
  adduser busybox dbus dmsetup file libaudit0 libcap2 libcryptsetup4 libdbus-1-3 libdevmapper1.02.1 libexpat1 libgcrypt11 libgpg-error0 libgpm2 libkmod2
  libmagic1 libncursesw5 libpam-systemd libpci3 libprocps0 libsqlite3-0 libssl1.0.0 libsystemd-daemon0 libsystemd-id128-0 libsystemd-journal0
  libsystemd-login0 libudev0 libusb-1.0-0 libwrap0 mime-support pciutils procps psmisc python python-minimal python2.7 python2.7-minimal sudo systemd
  systemd-sysv tcpd udev usbutils
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
  sysvinit

[Ian Wienand (iwienand)]

hmm, well I put this back in, but it seems like the bootloader is broken for wheezy

---
root@dib-xenial:/boot/grub# /usr/sbin/grub-install '--modules=biosdisk part_msdos' --force /dev/loop8
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/mapper/loop8p1. Check your device.map.
Auto-detection of a filesystem of /dev/mapper/loop8p1 failed.
Try with --recheck.
If the problem persists please report this together with the output of "/usr/sbin/grub-probe --device-map="/boot/grub/device.map" --target=fs -v /boot/grub" to <email address hidden>
root@dib-xenial:/boot/grub# /usr/sbin/grub-probe --device-map="/boot/grub/device.map" --target=fs -v /boot/grub
/usr/sbin/grub-probe: info: Scanning for dmraid_nv RAID devices on disk hd0.
/usr/sbin/grub-probe: info: the size of hd0 is 167772160.
/usr/sbin/grub-probe: info: the size of hd0 is 167772160.
/usr/sbin/grub-probe: info: scanning hd0 for LVM.
/usr/sbin/grub-probe: info: the size of hd0 is 167772160.
/usr/sbin/grub-probe: info: no LVM signature found.
/usr/sbin/grub-probe: info: the size of hd0 is 167772160.
/usr/sbin/grub-probe: info: Scanning for mdraid09 RAID devices on disk hd0.
/usr/sbin/grub-probe: info: the size of hd0 is 167772160.
/usr/sbin/grub-probe: info: the size of hd0 is 167772160.
/usr/sbin/grub-probe: info: Scanning for mdraid1x RAID devices on disk hd0.
/usr/sbin/grub-probe: info: the size of hd0 is 167772160.
/usr/sbin/grub-probe: info: the size of hd0 is 167772160.
/usr/sbin/grub-probe: info: Scanning for mdraid09 RAID devices on disk hd0.
/usr/sbin/grub-probe: info: the size of hd0 is 167772160.
/usr/sbin/grub-probe: info: the size of hd0 is 167772160.
/usr/sbin/grub-probe: info: Scanning for mdraid09 RAID devices on disk hd0,msdos1.
/usr/sbin/grub-probe: info: the size of hd0 is 167772160.
/usr/sbin/grub-probe: info: Scanning for mdraid1x RAID devices on disk hd0.
/usr/sbin/grub-probe: info: the size of hd0 is 167772160.
/usr/sbin/grub-probe: info: the size of hd0 is 167772160.
/usr/sbin/grub-probe: info: Scanning for mdraid1x RAID devices on disk hd0,msdos1.
/usr/sbin/grub-probe: info: the size of hd0 is 167772160.
/usr/sbin/grub-probe: info: scanning hd0 for LVM.
/usr/sbin/grub-probe: info: the size of hd0 is 167772160.
/usr/sbin/grub-probe: info: no LVM signature found.
/usr/sbin/grub-probe: info: the size of hd0 is 167772160.
/usr/sbin/grub-probe: info: scanning hd0,msdos1 for LVM.
/usr/sbin/grub-probe: info: the size of hd0 is 167772160.
/usr/sbin/grub-probe: info: no LVM signature found.
/usr/sbin/grub-probe: info: changing current directory to /dev/mapper.
/usr/sbin/grub-probe: info: changing current directory to /dev/mapper.
/usr/sbin/grub-probe: info: changing current directory to /dev/mapper.
/usr/sbin/grub-probe: info: no mapping exists for `/dev/mapper/loop8p1'.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/mapper/loop8p1. Check your device.map.
---

I really don't have the inclination to look into this ... it may have been broken for some time because I don't think we were ever testing "stable" ... only testing (which has become stretch)

There's a few bugs out there on this, but they talk about dm-crypt and lvm and things we're not exac...