Dear Maintainer,

   * What led up to the situation?

After an upgrade from bullseye to bookworm, sysv-rc-conf was tagged
as upgrading possible.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Using synaptic I tried to upgrade it but it ranted throwing a long
list of packages it wanted to uninstall, such as colord, gparted,
haruna, gufw, etc, however when I check those 4 they have been
upgraded correctly and moreover do not show any dependency with
sysv-rc-conf !

   * What was the outcome of this action?

I backed off.

   * What outcome did you expect instead?

sysv-rc-conf to upgrade smoothly, not trying to remove at least
30 packages that don't know it.

Ziziz vely stlange, limit weild.

Cheers,

Jean-Yves

Same here on multiple Debian/KDE machines after upgrading to Debian12. I think the title should be clearer or should this package actually be installed? I doubt it. For me it wants to remove way more than 30 packages, many of them being essential packages.

See https://unix.stackexchange.com/questions/748950/after-upgrading-to-debian12-and-upgrading-packages-apt-shows-the-following-pack Also this issue tracker is totally outdated. By decades. And nearly unusable, which is a problem if the project is interested in getting more devs involved.

Hello,

Bug #1042467 in sysv-rc-conf reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/sysv-rc-conf/-/commit/194a9a125c18753f0732f110f1c95c83100ca4b3
sysv-rc-conf was made to 'Depends' on sysvinit-core (later weakened to a
'Conficts' on systemd) in order to address #859693 and #791689. The objective
was to stop users being confused into thinking that sysv-rc-conf could control
their systemd-orchestrated services. As can be seen in the big drop in popcon
after the Bookworm release this did have some of the desired effect.

Unfortunately, since then there have been numerous counts of confusion
(which one can find with a simple web search) whereby users find this package
is 'held back' and attempts to resolve this can lead to apt suggesting
changing init systems.

New mitigations in this release reduce the need for the previous constraints:

  1. The new sysv-rc-conf displays a warning to users on every
     invocation while systemd is acting as the init system.

  2. A NEWS entry advises relevant user to uninstall this package.

Since there is no technical reason for this package not to co-exist with
systemd, however useless it might be in that context, and new mitigations exist
to avoid the original confusion, this commit removes the conflict and allows
this package to be upgraded where it has been held back.
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042467

Control: tag -1 - pending
[...]
because I had not realised that

https://salsa.debian.org/systemd-team/systemd/-/commit/79602fc225bcb3b5d57fd2a2c877439371480802

had happened and sysv-rc-conf depends on sysv-rc. Apparently having this
installed with systemd-sysv "causes problems". Not sure what those
problems are - mostly this package consists of README files!

Apologies for the error.

Control: tag -1 - pending
[...]
because I had not realised that

https://salsa.debian.org/systemd-team/systemd/-/commit/79602fc225bcb3b5d57fd2a2c877439371480802

had happened and sysv-rc-conf depends on sysv-rc. Apparently having this
installed with systemd-sysv "causes problems". Not sure what those
problems are - mostly this package consists of README files!

Apologies for the error.

Hello,

Bug #1042467 in sysv-rc-conf reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/sysv-rc-conf/-/commit/516ecaaf1d9a58060f6fc6e703898f448eb66888

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042467

[...]
[...]
[...]

I just tested a bullseye to bookworm to trixie upgrade with systemd and
sysv-rc-conf installed and the upgrade to trixie kicked out sysv-rc-conf
as a side effect of a new conflict by systemd on sysv-rc [1].

I think this problem can now be considered satisfactorily resolved when
affected users eventually upgrade to trixie.

In the meantime, explicitly uninstalling sysv-rc-conf is the workaround
for bookworm users.

I had been planning a notice in the NEWS for the next sysv-rc-conf
advising systemd users to uninstall but I think this may no longer be
necessary since such users will already be shaken out. (There will also
be a runtime check now.)

[1] https://salsa.debian.org/systemd-team/systemd/-/commit/79602fc225bcb3b5d57fd2a2c877439371480802