Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: wicket on 2014/03/23, 19:49:44
-
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.
-
At the moment your only choice is: puge siduction-base and use sysvinit. We will fix the manual- and base-package eventually. But in the long run i don't think that we will active support sysvinit any longer. We will not make any dependencies to systemd if not needed - and there will be only a handful of packages require systemd. But for these package we are not willing nor have the manpower to provide support for systemd and sysvinit.
-
Thank you very much for your prompt and informative reply.
Purging sidu-base sounds like good solution. From the package description it seems to be a toolkit for Django GUI applications, so it's not as critical as the package name had me believe. The only package I have installed that is dependent on sidu-base is sidu-disk-cente which I don't need either.
I appreciate that you have limited manpower which means that you can only support one init system. As long you don't intentionally do anything that might break SysV init or introduce any critical dependencies on systemd, I'll continue to be a happy siduction user.
-
Hello wicket,
thanks for your commitment.
A bug has been opened in the siduction bugtracker for this issue.
Bug #1525 (New): sidu-manual must not depend on systemd for the server-package
greetings
musca
-
I got the same error as wicket. What are the repercussions of not purging sidu-base?
-
Our manual depends on it.
greetz
devil
-
I got the same error as wicket. What are the repercussions of not purging sidu-base?
sidu-base and any packages that depend on it will not be updated. dist-upgrade will continue to fail until the bug is resolved, you purge sidu-base or you switch to systemd.
-
We suggest the second :P
-
Thank you all for your replies.
-
We suggest the second :P
I was hoping to read the manual to see how to convert to systemd! Any way to circumvent this catch22?
-
Where is the Catch 22? We are no pilots ....
apt-get install systemd sytemd-sysv libpam-systemd systemd-ui
should solve your problems.
If you want use systemd-jounal - thats easy too:
addgroup --system systemd-journal
mkdir -p /var/log/journal
chown root:systemd-journal /var/log/journal
gpasswd -a $user systemd-journal
done.
At your wish, purge the old rsyslog.
Finally: PRAY and reboot - the order of praying and doing the reboot doesn't really matter 8)
-
Catch 22 was I needed sidu-base to read the manual on how to convert to systemd . . . but sidu-base required systemd which I wanted to move to . . . . but thanks for the information and to irc earlier
Finally: PRAY and reboot - the order of praying and doing the reboot doesn't really matter
:D
-
sidu-base and any packages that depend on it will not be updated. dist-upgrade will continue to fail until the bug is resolved, you purge sidu-base or you switch to systemd.
I should have also mentioned that you can also hold the package back until the bug is resolved:
# echo "sidu-base hold" | dpkg --set-selections
I've just had to do this for network-manager which is now dependent on systemd (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743128). :(
-
sidu-base has just been split in 2 packages, sidu-manual will be soon. That should solve the bug.
greetz
devil
-
@wicket Just an FYI, learned this from devil. Instead of the old way of putting a package on hold, just do:
apt-mark hold sidu-baseSeems that apt is a lot smarter.
-
...But in the long run i don't think that we will active support sysvinit any longer. We will not make any dependencies to systemd if not needed - and there will be only a handful of packages require systemd. But for these package we are not willing nor have the manpower to provide support for systemd and sysvinit.
How much of an advance notice will be provided to users when the decision is made to no longer support sysvinit?
-
Finally: PRAY and reboot - the order of praying and doing the reboot doesn't really matter 8)
Have there been issues for users who have switched to systemd?
-
Performed a d-up a few minutes ago under LXDE and the issue with sidu-base seems to have been fixed. I didn't get any error messages and sidu-base was included among the packages updated.
-
sidu-base was a accident - we have not much packages with dependencies to a special init in installed systems. And our build scripts at the moment rely heavy on sysvinit - but that are run once scripts and will be mostly removed after the iso-build is done.
a few other scripts depend on sysvinit in the live iso - but as far as we can see run ok with systemd - but they will be changed. So the switch to systemd was not a big deal for us.
The decision to run with systemd in the future was short and hard: We had the choice to drop our gnome flavour or sysvinit. After a few intensive tests we decided do let sysvinit go 8) - Thats all.
-
Where is the Catch 22? We are no pilots ....
apt-get install systemd sytemd-sysv libpam-systemd systemd-ui
should solve your problems.
hey, I've tried this but got an error (with 0 results on google :/ )
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package sytemd-sysv
any idea what is going on?
(I executed apt-get update before)
-
hey, I've tried this but got an error (with 0 results on google :/ )
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package sytemd-sysv
"systemd" has 2 "s" in it.
-
hey, I've tried this but got an error (with 0 results on google :/ )
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package sytemd-sysv
"systemd" has 2 "s" in it.
right, thank you for your observation! I just copy/pasted it without looking at it