Your message dated Sat, 9 Aug 2025 10:03:04 +0100
with message-id <[email protected]>
and subject line Re: Bug#1042467: sysv-rc-conf: from bullseye want to uninstall 
many packages without dependency when trying upgrading it
has caused the Debian Bug report #1042467,
regarding sysv-rc-conf: from bullseye want to uninstall many packages without 
dependency when trying upgrading it
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.)


-- 
1042467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042467
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sysv-rc-conf
Version: 0.99-7.1
Severity: normal

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


-- System Information:
Debian Release: 12.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-10-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (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 sysv-rc-conf depends on:
ii  libcurses-ui-perl  0.9609-1.1
ii  sysv-rc            3.06-4

sysv-rc-conf recommends no packages.

sysv-rc-conf suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
On Fri, Jul 28, 2023 at 07:33:41PM +0200, Jiff wrote:
> After an upgrade from bullseye to bookworm, sysv-rc-conf was tagged
> as upgrading possible.
[...]
> 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 !
[...]
> Debian Release: 12.1
[...]
> Init: systemd (via /run/systemd/system)

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

--- End Message ---

Reply via email to