The issue is still there: when I try to apt install git-all on my fresh Ubuntu 16.04 install, runit crashes with an output similar to @tony.vandenhaag, without any reference to dconf-tools or any package other than runit and git-daemon-run.
Apparently, it's a problem with the postinst (post installation) script in the upstream "runit" package that is attempting to configure runit for BOTH systemd AND upstart, but though upstart is installed, it's NOT the active init system so upstarts "/sbin/start runsvdir" fails, the postinst script throws an error, and dpkg stops the installation/configuration.
Solution:
- In file /var/lib/dpkg/info/runit.postinst, comment lines
if [ -x /sbin/start ]; then #provided by upstart
/sbin/start runsvdir
fi
- Save and quit
- Finish runit installation by running sudo dpkg --configure -a
- Uncomment previously commented lines
The issue is still there: when I try to apt install git-all on my fresh Ubuntu 16.04 install, runit crashes with an output similar to @tony.vandenhaag, without any reference to dconf-tools or any package other than runit and git-daemon-run.
I found the solution is this thread: /forum. peppermintos. com/index. php?topic= 5210.0
https:/
Apparently, it's a problem with the postinst (post installation) script in the upstream "runit" package that is attempting to configure runit for BOTH systemd AND upstart, but though upstart is installed, it's NOT the active init system so upstarts "/sbin/start runsvdir" fails, the postinst script throws an error, and dpkg stops the installation/ configuration.
Solution: dpkg/info/ runit.postinst, comment lines
- In file /var/lib/
if [ -x /sbin/start ]; then #provided by upstart
/sbin/start runsvdir
fi
- Save and quit
- Finish runit installation by running sudo dpkg --configure -a
- Uncomment previously commented lines