Your message dated Sun, 9 Nov 2014 18:34:34 +0000 with message-id <20141109183434.ga11...@reptile.pseudorandom.co.uk> and subject line Re: Bug#757588: #757588: sysvinit-core: installation fails when systemd is present has caused the Debian Bug report #757588, regarding sysvinit-core: installation fails when systemd is present to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 757588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: sysvinit-core Version: 2.88dsf-53.3 Severity: critical Tags: d-i Justification: breaks the whole system A dist-upgrade done last week replaced, without asking, sysvinit by systemd that I do not want to use. I checked which packages were available for reinstalling sysvinit and found sysvinit-core. I installed it (and sysvinit-utils) with apt-get and got an error because systemd was running. On reboot the system went on single user because /sbin/init was not available. I tried to run systemd and got an error message saying that the system was booted by sysvinit. I recovered from this situation by using a Live CD to copy the files in the package data.tar to the system disk. In my opinion there are two problems here: - the hidden installation of systemd and removal of sysvinit (I am aware this should be a bug report on systemd...) - the loose way the sysvinit-core is installed by not taking heed in an appropriate way of an error that breaks the system, leaving it with no process launcher. Best regards, Miguel Filgueiras -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages sysvinit-core depends on: ii debconf [debconf-2.0] 1.5.50 ii debianutils 4.3.4 ii initscripts 2.88dsf-41 ii libc6 2.17-3 ii libselinux1 2.1.13-2 ii libsepol1 2.1.9-2 ii sysv-rc 2.88dsf-41 ii sysvinit-utils 2.88dsf-41 sysvinit-core recommends no packages. sysvinit-core suggests no packages. -- debconf information excluded
--- End Message ---
--- Begin Message ---Version: 2.88dsf-57 On Sat, 08 Nov 2014 at 13:41:44 +0200, Damyan Ivanov wrote: > I was unable to reproduce this with the current sysvinit package in > jessie (2.88dsf-57). I've done some similar testing recently with the same result; marking the bug as fixed. On Sat, 08 Nov 2014 at 12:47:28 +0000, Miguel Filgueiras wrote: > I am not happy with the way this bug, marked as critical, > was dealt with: it took 3 months to be attended to That's unfortunate, but there's nothing anyone can do about it now. S
--- End Message ---
