Your message dated Mon, 23 Feb 2026 09:09:55 +0300
with message-id
<cajtv3cp6woyppohqknrwfgt5s9dwelynaw6ibfdshnp0-ec...@mail.gmail.com>
and subject line Re: Bug#1128351: Cannot install sysvinit-core on a fresh
Trixie installation (13.2)
has caused the Debian Bug report #1128351,
regarding Cannot install sysvinit-core on a fresh Trixie installation (13.2)
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 [email protected]
immediately.)
--
1128351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1128351
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sysvinit-core
Version: 3.14-4
Severity: grave
X-Debbugs-Cc: [email protected]
After a fresh installation of my virtual server, I wanted to switch sysv as I
always do however, I couldn't do so:
root@vmi3092844:~# apt install sysvinit-core orphan-sysvinit-scripts
Solving dependencies... Error!
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
Unsatisfied dependencies:
initscripts : Depends: sysv-rc but it is not going to be installed or
file-rc but it is not installable or
openrc but it is not going to be installed
systemd-sysv : Conflicts: initscripts but 3.14-4 is to be installed
Conflicts: orphan-sysvinit-scripts but 0.21+deb13u2 is to be
installed
Conflicts: sysvinit-core but 3.14-4 is to be installed
Recommends: libnss-systemd but it is not going to be installed
sysvinit-core : Depends: sysv-rc but it is not going to be installed or
file-rc but it is not installable or
openrc but it is not going to be installed
Conflicts: systemd-sysv but 257.9-1~deb13u1 is to be installed
Error: Error, pkgProblemResolver::Resolve generated breaks, this may be caused
by held packages.
Error: The following information from --solver 3.0 may provide additional
context:
Unable to satisfy dependencies. Reached two conflicting decisions:
1. systemd-sysv:amd64 is selected for install
2. systemd-sysv:amd64 is selected for removal because:
1. sysvinit-core:amd64=3.14-4 is selected for install
2. systemd-sysv:amd64 Conflicts sysvinit-core
I tried to force remove systemd-sysv and eventually libpam-systemd but nothing
resolved it. I don't this was an issue in 13.0. I'm not 100% sure but
definitely managed to switch in 12.x
-- System Information:
Debian Release: 13.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.38+deb13-cloud-amd64 (SMP w/6 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages sysvinit-core depends on:
pn initscripts <none>
ii libc6 2.41-12+deb13u1
ii libselinux1 3.8.1-1
ii mount 2.41-5
pn sysv-rc | file-rc | openrc <none>
ii sysvinit-utils 3.14-4
Versions of packages sysvinit-core recommends:
pn orphan-sysvinit-scripts <none>
Versions of packages sysvinit-core suggests:
pn bootlogd <none>
--- End Message ---
--- Begin Message ---
Hi all, I updated the wiki as best as I could. Thanks again for all your
help.
--
aldemir
On Thu, 19 Feb 2026 at 21:31, Thorsten Glaser <[email protected]> wrote:
> On Thu, 19 Feb 2026, Andrew Bower wrote:
>
> >On Thu, Feb 19, 2026 at 09:49:39AM +0300, Aldemir Akpinar wrote:
>
> >> (Reading database ... 27088 files and directories currently
> installed.)
> >> Removing systemd (257.9-1~deb13u1) ...
> >> systemd is the active init system, please switch to another before
> >> removing systemd.
> >
> >I don't believe you needed to include 'systemd-' in this command line -
> >you do that as a second step after reboot, as before.
>
> Ah, oops. I install systems with debootstrap these days and always
> change inits before booting into them, so I forgot.
>
> >I don't think this is necessary. Sorry, I think the wiki page needs
> >rewriting.
>
> Yes, definitely.
>
> >I have never done this - perhaps it was necessary in the
> >past. It seems the optimal instructions are a hybrid of the "at
> >installation time" and "at runtime" instructions.
>
> No. We truly need separate instructions per Debian release,
> especially as apt also changed (it doesn’t show the “Yes, do
> as I say!” prompt any more, just fails to do what the user
> requested, and the manpage explicitly doesn’t say that the
> fix for that is --allow-remove-essential, and the maintainer
> thinks that’s okay… 😾
>
> >> I used to do an apt-get install sysvinit-core, reboot, and apt-get
> >> remove systemd. It always worked from jessie to bookworm.
> >
> >Sorry for having directed you to the wiki when it merely added confusion
> >- I didn't realise how out of date it was.
>
> Yeah, we really need updated instructions. Probably best
> also include o-s-s, as that has become good as mandatory
> with at least bookworm.
>
> >> I feel like debian doesn't care about choice anymore, becoming just
> >> another redhat clone.
>
> Yeah… we literally got told that Debian “was never about choice” 😿
>
> >ifupdown is already "Priority: important" so I'm not sure why you didn't
> >have it already installed.
>
> New installs won’t have it any more, they now use network-manager on
> one kind of installs and netplan(?) or something else even worse on
> others (one is servers, the other is desktops/laptops, I forgot which
> is which, dropped it and installed ifupdown as I wanted).
>
> Note that trixie has udhcpc-base instead of isc-dhcp-client by default
> as the latter is EOL since 2021 and not security-supported in trixie
> any more, but this will also cause trouble and changes. The ifupdown
> maintainer tries his best to get things working, but this really needs
> patches in udhcpc, which the udhcpc maintainer refuses to even discuss.
> 🤬 But in trixie at least, you can still install isc-dhcp-client on
> systems you don’t want these experiments on.
>
> Point of order, I don’t think this is a bug in the package, and we
> probably should control-close this. However, we NEED a working wiki
> page, and I’d like to suggest another improvement: the Description
> field of the relevant binary package(s) should gain a paragraph to
> say that a normal apt-get install will not work with them on systems
> currently booted with another init, that that is expected, and that
> the wiki page (URL here) contains the necessary procedure.
>
> I think this could even get into stable-p-u.
>
> bye,
> //mirabilos
> --
> Yes, I hate users and I want them to suffer.
> -- Marco d'Itri on gmane.linux.debian.devel.general
>
--- End Message ---
