# not reproducible on maintainer's system tags 856024 unreproducible thanks
On 17 April 2017 at 18:59, Jonas Smedegaard <d...@jones.dk> wrote: > I don't recall, but believe I installed using plain standard > debian-installer with the "netboot" image. But possibly I might have > used multistrap, which means the order of installing the various > packages may be different from (c)debootrap-based installs. Something > that is *not* a bug in multistrap - Debian Policy mandates package > relations but no specific install order. Thanks - I'll break out some real armhf hardware later. So far I've mainly been testing by reinstalling rather than upgrading systemd-sysv. I don't *think* multistrap install order should be an issue - I've even tried uninstalling systemd-sysv in a chroot (so that /sbin/halt doesn't exist), installing molly-guard, then installing systemd-sysv again - but this seemed to be handled fine. If you used multistrap, does this mean there was another package repo involved? The bit I can't get my head round is why dpkg-divert would not have reported molly-guard having any diversions in place (which seems to match the error message "also in package molly-guard 0.6.4"). For any recently-installed stretch system, molly-guard should definitely have been using diversions. -- Tim Retout <dioc...@debian.org>
