reassign 856024 multistrap forcemerge 591518 856024 kthxbye It appears multistrap has longstanding issues with dpkg-divert, e.g.:
- https://lists.debian.org/debian-embedded/2010/04/msg00025.html - https://bugs.launchpad.net/ubuntu/+source/multistrap/+bug/646901 (in Ubuntu, but same issue) I don't think there's anything specifically wrong with how molly-guard is using dpkg-divert, so I'm merging this bug in with the relevant multistrap bug (#591518). Hope that's all right. Kind regards, On 18 April 2017 at 15:28, Tim Retout <dioc...@debian.org> wrote: > tags 856024 - unreproducible > thanks > > On 18 April 2017 at 13:53, Jonas Smedegaard <d...@jones.dk> wrote: >> Possibly this (sub)issue is tied to this: >> >> 1) install both packages _without_ executing postinst >> while *not* running systemd (e.g. in a chroot) >> 2) execute postinst of each package (in varying order) >> while *not* running systemd (e.g. in a chroot) >> 3) run systemd (e.g. boot the system on real hardware) >> 4) update systemd-sysv > > Okay, please find attached a multistrap config for helping to > reproduce this on amd64. > > $ sudo multistrap -f config > $ sudo cp /var/cache/apt/archives/systemd-sysv_232-22_amd64.deb > /opt/multistrap/ > $ sudo chroot /opt/multistrap > # dpkg --configure -a # I chose "Europe/London" as timezone when > prompted, and did not make dash the default shell > # dpkg -i systemd-sysv_232-22_amd64.deb > > Produces this output: > > (Reading database ... 7170 files and directories currently installed.) > Preparing to unpack systemd-sysv_232-22_amd64.deb ... > Unpacking systemd-sysv (232-22) over (232-22) ... > dpkg: error processing archive systemd-sysv_232-22_amd64.deb (--install): > trying to overwrite '/sbin/halt', which is also in package molly-guard 0.6.4 > Errors were encountered while processing: > systemd-sysv_232-22_amd64.deb > > I think this happens because molly-guard's preinst was not run - I > also had troubles with dash's /bin/sh diversion, hence choosing "no" > in the instructions above. > > Jonas: is there a step in your install process where preinst scripts get run? > > If this is the issue, I'm now trying to work out what to do about > it... the preinst does seem to be the right place according to Policy > Appendix G. > > Kind regards, > > -- > Tim Retout <dioc...@debian.org> -- Tim Retout <dioc...@debian.org>
