Your message dated Tue, 23 Mar 2021 17:41:57 +0000
with message-id <[email protected]>
and subject line Re: Bug#932290:
has caused the Debian Bug report #932290,
regarding insserv: Script has overlapping Default-Start and Default-Stop
runlevels
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.)
--
932290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932290
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: insserv
Version: 1.20.0-1
Severity: important
Dear insserv maintainers,
upgrading the system lead to several warnings from insserv; maybe this is a
duplicate of
932199, but i have some additional lines related to rsync, lvm2 and apparmor
[...]
Unpacking initscripts (2.95-1) over (2.95-1) ...
Preparing to unpack .../10-libassuan0_2.5.3-6_amd64.deb ...
Unpacking libassuan0:amd64 (2.5.3-6) over (2.5.3-6) ...
Setting up anacron (2.3-29) ...
insserv: warning: could not find all dependencies for $portmap
insserv: warning: could not find all dependencies for $portmap
insserv: warning: could not find all dependencies for $portmap
insserv: warning: could not find all dependencies for $portmap
insserv: Script rsync has overlapping Default-Start and Default-Stop runlevels
(2 3 4 5) and (2 3 4 5). This should be fixed.
insserv: Script lvm2 has overlapping Default-Start and Default-Stop runlevels
(S) and (S). This should be fixed.
insserv: Script apparmor has overlapping Default-Start and Default-Stop
runlevels (S) and (S). This should be fixed.
Setting up hdparm (9.58+ds-2) ...
[...]
I'm not sure why it detects that start and stop runlevels are overlapping, all
rsync lvm2 and apparmor
have empty 'Default-Stop' field in the header like this
### BEGIN INIT INFO
# Provides: apparmor
# Required-Start: $local_fs
# Required-Stop: umountfs
# Default-Start: S
# Default-Stop:
# Short-Description: AppArmor initialization
Downgrading insserv to 1.18.0-2 fix the issue for me
Lorenzo
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.20.3-van (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
Versions of packages insserv depends on:
ii libc6 2.28-10
insserv recommends no packages.
Versions of packages insserv suggests:
pn bootchart2 <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
version: 1.21.0-1.1
On 22/03/2021 01:38, Matteo Croce wrote:
On Sun, Mar 21, 2021 at 12:38 PM Matthew Vernon <[email protected]> wrote:
Have you upgraded to the later version of insserv? And if so, has this
resolved the problem for you?
How to trigger it? Maybe with:
apt --reinstall install rsync
In case, I don't get any warning.
Cool, thanks for confirming (I was reasonably confident, but it's nice
to check before closing :) )
Regards,
Matthew
--- End Message ---
