On Sun, Mar 21, 2021 at 12:38 PM Matthew Vernon 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.
Regards,
--
per aspera ad upstream
On 04/03/2021 14:20, Matthew Vernon wrote:
On 04/03/2021 14:01, Matteo Croce wrote:
On Thu, Mar 4, 2021 at 2:53 PM Matthew Vernon wrote:
On 04/03/2021 13:36, Matteo Croce wrote:
I'm seeing it multiple times now during an upgrade:
Which version of insserv have you got? 1.21.0-1.1 (which we
On 04/03/2021 14:01, Matteo Croce wrote:
On Thu, Mar 4, 2021 at 2:53 PM Matthew Vernon wrote:
On 04/03/2021 13:36, Matteo Croce wrote:
I'm seeing it multiple times now during an upgrade:
Which version of insserv have you got? 1.21.0-1.1 (which we expect to
fix this) isn't yet in testing.
On Thu, Mar 4, 2021 at 2:53 PM Matthew Vernon wrote:
>
> Hi,
>
> On 04/03/2021 13:36, Matteo Croce wrote:
> > I'm seeing it multiple times now during an upgrade:
>
> Which version of insserv have you got? 1.21.0-1.1 (which we expect to
> fix this) isn't yet in testing.
>
ii insserv
Hi,
On 04/03/2021 13:36, Matteo Croce wrote:
I'm seeing it multiple times now during an upgrade:
Which version of insserv have you got? 1.21.0-1.1 (which we expect to
fix this) isn't yet in testing.
Regards,
Matthew
I'm seeing it multiple times now during an upgrade:
Setting up initscripts (2.96-6) ...
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 rsync has overlapping Default-Start and Default-Stop runlevels
(2
Same issue here. I get the following output when upgrading initscripts:
Preparing to unpack .../07-initscripts_2.96-5_all.deb ...
Unpacking initscripts (2.96-5) over (2.96-4) ...
(...)
Setting up initscripts (2.96-5) ...
Installing new version of config file /etc/init.d/mountdevsubfs.sh ...
When I applied the patch provided above it causes insserv to segfault
when running the testsuite (make check). Looks like the program is
crashing using one of the LSB header checks. I haven't looked into it in
any detail yet, but it seems moving that check to a sooner point causes
a memory issue.
control: tags -1 +confirmed +help +upstream +patch
[2019-07-24 14:12] Lorenz
> Control: severity -1 normal
>
> Ok, here is what I've found out; to reproduce the issue you need to
> disable with update-rc.d a script that has an empty ' Default-Stop: ' field
> in the LSB header.
> [...]
Yes, I
Control: severity -1 normal
Ok, here is what I've found out; to reproduce the issue you need to
disable with update-rc.d a script that has an empty ' Default-Stop: ' field
in the LSB header.
# update-rc.d ssh disable
insserv: warning: current start runlevel(s) (empty) of script `ssh'
overrides
[2019-07-21 15:36] Lorenz
> Il giorno gio 18 lug 2019 alle ore 14:45 Dmitry Bogatov
> ha scritto:
> >Are there overrides in /etc/insserv/overrides/? Does this warning
> >appear if you invoke:
> >
> > 1. # insserv
> > 2. # insserv apparmor
> > 3. If either 1. or 2. reproduces problem, please
control: tags -1 +help +moreinfo
[2019-07-17 13:25] Lorenzo Puliti
> [...]
> insserv: Script rsync has overlapping Default-Start and Default-Stop
> runlevels (2 3 4 5) and (2 3 4 5). This s
> hould be fixed.
> insserv: Script lvm2 has overlapping Default-Start and Default-Stop runlevels
>
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
13 matches
Mail list logo
