0 Members and 1 Guest are viewing this topic.
systemd[some number]: Job dbus.socket/start deleted to break ordering cycle starting with sockets.target/startsystemd[some number]: Job dbus.socket/start deleted to break ordering cycle starting with sockets.target/startsystemd[some number]: Job dbus.socket/start deleted to break ordering cycle starting with sockets.target/startsystemd[some number]: Job dbus.socket/start deleted to break ordering cycle starting with sockets.target/startetc...
# apt-show-versions -u :(libsystemd-daemon0:amd64/unstable 204-6 upgradeable to 204-10libsystemd-journal0:amd64/unstable 204-6 upgradeable to 204-10libsystemd-login0:amd64/unstable 204-6 upgradeable to 204-10network-manager:amd64/unstable 0.9.8.0-5 upgradeable to 0.9.8.10-1phonon-backend-vlc:amd64/unstable 0.6.2-2 upgradeable to 0.7.1-1systemd:amd64/unstable 204-6 upgradeable to 204-10systemd-sysv:amd64/unstable 204-6 upgradeable to 204-10
root@imerabox:/# apt-cache policy systemdsystemd: Installed: 204-10 Candidate: 204-10 Version table: 208-1 0 1 http://ftp.us.debian.org/debian/ experimental/main amd64 Packages *** 204-10 0 500 http://ftp.us.debian.org/debian/ unstable/main amd64 Packages 100 /var/lib/dpkg/status 204-5.2 0 500 http://packages.siduction.org/fixes/ unstable/main amd64 Packages
apt updateapt install libsystemd-daemon0apt install libsystemd-journal0apt install libsystemd-login0apt install systemdapt install systemd-sysvapt install network-managerapt install phonon-backend-vlc
I'm not using systemd at the moment, but I've read of some issues with the package in the past few weeks and I believe Linus Torvalds recently ranted about it. I wonder if the Debian folks have made the best/right decision in going with it for the next stable release.
Linus' continued work on the kernel is great, his ranting totaly irrelevant to us.
That seems a strange reply, his rant was about bugs introduced into systemd by the maintainer ...
@dibl : I tried deinstalling systemd reinstalling sysvinit, d-u, reinstalling systemd, and it's all the same, the system does not boot with the same error I posted. and worst : no error message during install or d-u...
...Quotesystemd[some number]: Job dbus.socket/start deleted to break ordering cycle starting with sockets.target/startetc......Thanks to having siduction installed on a btrfs subvolume it is quite simple to come back to a previous snapshot of my system....
systemd[some number]: Job dbus.socket/start deleted to break ordering cycle starting with sockets.target/startetc...
systemctl status dbus.targetsystemctl status dbus.socketsystemctl status sockets.targetsystemctl show dbus.socketsystemctl show sockets.target