Today I ran a dist-upgrade only to find that sidu-base could not be installed:
Setting up sidu-base (2014.03.07) ...
/usr/bin/sidu-control: line 19: systemctl: command not found
dpkg: error processing package sidu-base (--configure):
subprocess installed post-installation script returned error exit status 127
As you can see, the sidu-control shell script is dependent on the systemctl command which is part of systemd. I do not want to use systemd for various reasons (which I won't detail here) and I have chosen to continue using System V init system for the time being. Despite Debian choosing to use systemd as the default init system for Jessie, they will continue to give users the freedom of choice and System V init will continue to be supported. Is this not the case for siduction? I had assumed it was as I was never forced to install systemd. Either way, the package is broken because even if you have given up on supporting SysV init, there is a dependency on systemd and it should be specified in the package dependencies.
I do hope you haven't given up on those of us still using SysV init so I can continue using this great distro, however I will sooner switch distros than lose my freedom of choice.
Cheers.