Bug#940965: apt: Fails to find a solution for libgtk-3-0 and sysvinit-core
lorenzo
plorenzo at disroot.org
Tue Feb 18 15:24:45 GMT 2025
Dear apt maintainers,
> On Sun, Feb 16, 2025 at 12:23:01PM +0100, Julian Andres Klode wrote:
> > That being said, being able to switch init systems without a pin is
> > a bug in the init system; init systems should set the Protected: yes
> > field so that they cannot be removed without explicitly running
> >
> > apt remove --allow-remove-essential sysvinit-core
Mmm, and what if the package is at the bottom of a dependency stack? do
you get all the stack removed as well?
> > apt install/upgrade/... --allow-remove-essential sysvinit-core-
> >
> > (note that starting with 2.3.12/stable; --allow-remove-essential
> > only applies to arguments; the solver itself cannot decide to
> > remove essential packages anymore)
how a user is supposed to perform an init switch? use dpkg
--force-depends and manually fix the broken dependency stack without
the help of a resolver?
Best,
Lorenzo
More information about the Debian-init-diversity
mailing list