Bug#574975: Not fixed

[Sebastian Zerbe]

Okay,

Guido Günther schrieb:
> On Tue, Mar 23, 2010 at 09:41:40AM +0100, Sebastian Zerbe wrote:
>   
>> I have the same problem and it is fixed neither in testing nor in
>> unstable. The dependencies are broken:
>>
>> Installing new version of config file /etc/init.d/multipath-tools-boot ...
>> Installing new version of config file /etc/init.d/multipath-tools ...
>> insserv: warning: current stop runlevel(s) (0 1 6) of script `ntp'
>> overwrites defaults (empty).
>> insserv: There is a loop between service lvm2 and
>> multipath-tools-boot if started
>> insserv:  loop involving service multipath-tools-boot at depth 6
>> insserv:  loop involving service module-init-tools at depth 5
>> insserv: There is a loop between service lvm2 and
>> multipath-tools-boot if started
>> insserv:  loop involving service checkfs at depth 3
>> insserv:  loop involving service lvm2 at depth 2
>> insserv:  loop involving service udev at depth 1
>> insserv: There is a loop between service checkfs and lvm2 if started
>> insserv:  loop involving service mountall at depth 5
>> insserv:  loop involving service mtab at depth 3
>> insserv: There is a loop between service mountall and checkfs if started
>> insserv:  loop involving service portmap at depth 17
>> insserv:  loop involving service networking at depth 18
>> insserv: exiting now without changing boot order!
>> update-rc.d: error: insserv rejected the script header
>> dpkg: error processing multipath-tools (--configure):
>> subprocess installed post-installation script returned error exit status 1
>> Errors were encountered while processing:
>> multipath-tools
>>
>>
>> Please provide a solution because I can't easily remove multipath-tools.
>>     
> I can reproduce this here by upgrading my test vm. However
> multipath-tools itself didn't change so it seems something else broke.
> Petter, any idea what's going on here?
> Cheers,
>  -- Guido
>
>
>
>   
as far as I can see, the LSB entries in module-init-tools changed:

 # Provides:          module-init-tools
 # Required-Start:   
 # Required-Stop:    
-# Should-Start:      checkroot
-# Should-stop:
+# Should-Start:      $local_fs
+# Should-Stop:
 # Default-Start:     S
 # Default-Stop:
 # Short-Description: Process /etc/modules.
 # Description:       Load the modules listed in /etc/modules.

Changing the Should-Start value back to "checkroot" fixes the problem, 
but I don't want to check for the implicationes on my live system...

Regards
Sebastian Zerbe