Bug#989284: insserv: toggles rc0.d/{K02avahi-daemon => K01avahi-daemon} with every upgrade

[Jesse Smith]

On 2021-09-26 2:37 p.m., Thorsten Glaser wrote:
> On Sun, 26 Sep 2021, Jesse Smith wrote:
>
>> did last time. This time please run"
>>
>> # insserv -v -s
>>
>> This should set avahi-daemon to K01. Then run
> Erm, well, it doesn’t. Apparently, the presence of -s prevents this.

You're right, that's my mistake. I forgot the "-s" flag will show what
insserv plans to do, but not actually update the symlinks.


>> # insserv -v -s -n
>>
>> This should tell us whether insserv wants to toggle avahi-daemon back to
>> K02, but without actually making any changes. And hopefully it will give
>> a clue as to why this is happening.Thank you.
> Maybe the attached will still suffice as clue?
>

Based on the output you shared it does indeed look like that whenever
avahi-daemon is set to K02, insserv wants to switch it back to K01. But
then when insserv is run again, without the -s or -n flags indicating a
dry run, it tries to switch things back from K01 to K02. This is indeed
strange.

I've tried this again on my own machine and cannot reproduce the
behaviour. I've tried both the latest version of insserv (1.23.0) and
the version which shipped with Debian 10 (1.18.0). I did notice having
other dependency trouble when I tested with insserv 1.21.0 which I
believe is the version being used when the bug is triggered?

Thorsten, I wonder if you could give the latest version of insserv a try
(version 1.23.0) which can be downloaded here:
https://download.savannah.nongnu.org/releases/sysvinit/insserv-1.23.0.tar.xz

Perhaps this is related to a previous dependency issue we already fixed
in 1.21.0. Or, if you're still experiencing the problem with insserv
1.23.0 then we've got a bigger mystery.

- Jesse