Your message dated Tue, 20 May 2025 12:47:26 +0200
with message-id <beac177a-e553-463f-95b2-a3bbaf636...@debian.org>
and subject line Re: Bug#1095600: gparted: Apt want to remove my init system
has caused the Debian Bug report #1079018,
regarding docker.io: Existing docker.io try to remove sysvinit at upgrade
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.)


-- 
1079018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: docker.io
Version: 20.10.25+dfsg1-3
Severity: important
X-Debbugs-Cc: bardot.jer...@gmail.com

Dear Maintainer,

Everything is in the title,
Current state lets users/administrators with no real choice :
- remove sysvinit OR
- not use docker.io package

Maybe there is a workaround or an other package to make the docker.io stuff ?
As today several software need or provide test version based on docker.

Thx


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.8.12-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to fr_FR.UTF-8), LANGUAGE=fr_FR.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages docker.io depends on:
ii  adduser                    3.137
ii  containerd                 1.7.18~ds1-6
ii  init-system-helpers        1.66
ii  iptables                   1.8.10-4
ii  libc6                      2.39-6
ii  libdevmapper1.02.1         2:1.02.196-1+b1
ii  libsystemd0                256.4-3
ii  lsb-base                   11.6
ii  runc                       1.1.12+ds1-2+b1
ii  sysvinit-utils [lsb-base]  3.10-1
ii  tini                       0.19.0-1

Versions of packages docker.io recommends:
ii  apparmor         3.1.7-1+b1
ii  ca-certificates  20240203
ii  cgroupfs-mount   1.4+nmu1
ii  git              1:2.43.0-1+b1
ii  needrestart      3.6-8
ii  xz-utils         5.6.2-2

Versions of packages docker.io suggests:
pn  aufs-tools                 <none>
ii  btrfs-progs                6.6.3-1.2+b1
ii  debootstrap                1.0.137
pn  docker-doc                 <none>
ii  e2fsprogs                  1.47.1-1
pn  rinse                      <none>
pn  rootlesskit                <none>
ii  xfsprogs                   6.8.0-2.2
pn  zfs-fuse | zfsutils-linux  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Thanks for the elaborate answer, Simon.

It appears Jerome has filed quite a few duplicates for other packages, about the same issue:

docker.io: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079018
synaptic: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093418
partitionmanager: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095601

I'm going to close all of them as duplicates with the same reasoning.

Regards,
Michael


On Tue, 20 May 2025 10:49:11 +0100 Simon McVittie <s...@debian.org> wrote:

On Sun, 09 Feb 2025 at 17:51:11 +0100, Bardot Jerome wrote:
>apt install --no-install-recommends gparted
...
>Installing dependencies:
>  dbus-user-session  libnss-systemd  libpam-systemd  pkexec  polkitd  systemd
>systemd-cryptsetup  systemd-sysv
>
>Paquets suggérés :
>  libtss2-rc0t64  systemd-container  systemd-homed  systemd-userdbd  systemd-
>boot  systemd-resolved  systemd-repart
>
>REMOVING:
>  initscripts  insserv  orphan-sysvinit-scripts  rcconf  startpar  systemd-
>standalone-sysusers  sysv-rc  sysv-rc-conf  sysvinit-core

You are using a non-default init system. This is a core system component and you cannot necessarily expect apt's heuristics for resolving dependencies to choose the answer that you want when you have swapped out core system components. You will need to give it more clues about what you want, for example

     apt install gparted systemd-

or

     apt install gparted sysvinit-core

to tell apt that installing systemd or removing sysvinit-core is not a dependency resolution that you consider to be valid, or

     apt install gparted libpam-elogind

to tell apt explicitly how to resolve the dependency on a logind implementation.

On Mon, 19 May 2025 at 12:38:58 -0400, Phillip Susi wrote:
>It appears that policykit hard depends on systemd.

No, it does not. It depends on functionality that in a typical Debian system is provided by systemd, but alternatives do exist.

polkitd (the package containing the polkit system service, previously called PolicyKit) depends on either adduser or an implementation of the systemd-sysusers interface, and either default-logind (libpam-systemd) or another implementation of the logind interface.

On sysvinit systems, these dependencies can be satisfied by installing adduser or systemd-standalone-sysusers instead of systemd, and installing libpam-elogind instead of libpam-systemd.

policykit-1 is a transitional package which no longer exists in testing/unstable. In stable, it depended on polkitd (the daemon) and pkexec (a sudo-like privilege elevation program with polkit integration).

     smcv

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to