Hi all,

> Package: console-common
> Version: 0.7.86
> Severity: serious
> 
> Installation of console-common 0.7.86 has failed in unstable for me with the
> following insserv error:

I'd like to think of it as a console-common error which causes insserv to
reject the keymap.sh script header causing dpkg to report an error state :)

> 
>   Setting up console-common (0.7.86) ...
>   Looking for keymap to install:
>   NONE
>   insserv: There is a loop between service checkfs and cryptdisks if started
>   insserv:  loop involving service cryptdisks at depth 12
>   insserv:  loop involving service checkroot at depth 11
>   insserv: There is a loop between service nfs-common and hwclock if started
>   insserv:  loop involving service hwclock at depth 12
>   insserv: There is a loop between service lvm2 and cryptdisks-early if 
> started
>   insserv:  loop involving service cryptdisks-early at depth 12
>   insserv: There is a loop between service checkfs and cryptdisks if started
>   insserv: There is a loop between service nfs-common and hwclock if started
>   insserv: There is a loop between service lvm2 and cryptdisks-early if 
> started
>   insserv:  loop involving service mountnfs at depth 8
>   insserv:  loop involving service nfs-common at depth 7
>   insserv:  loop involving service portmap at depth 6
>   insserv:  loop involving service mountall at depth 4
>   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:  loop involving service mtab at depth 13
>   insserv: There is a loop between service mountall and checkfs if started
>   insserv:  loop involving service keymap at depth 16
>   insserv:  loop involving service hibernate-cleanup at depth 20
>   insserv:  loop involving service networking at depth 22
>   insserv:  loop involving service restorecond at depth 32
>   insserv: There is a loop between service mountnfs and nfs-common if started
>   insserv:  loop involving service alsa-utils at depth 33
>   insserv:  loop involving service ifupdown-clean at depth 34
>   insserv:  loop involving service console-screen at depth 34
>   insserv: exiting now without changing boot order!
>   update-rc.d: error: insserv rejected the script header
>   dpkg: error processing console-common (--configure):
>    subprocess installed post-installation script returned error exit status 1
>   Errors were encountered while processing:
>    console-common

There is a change in dependency information in the keymap.sh init.d script of
console-common 0.7.86 that is not fully articulated in the changelog:

diff -Nru console-common-0.7.85/debian/keymap.sh 
console-common-0.7.86/debian/keymap.sh
--- console-common-0.7.85/debian/keymap.sh      2009-11-01 05:41:53.000000000 
+1000
+++ console-common-0.7.86/debian/keymap.sh      2011-12-05 01:05:31.000000000 
+1000
@@ -1,8 +1,8 @@
 #!/bin/sh
 ### BEGIN INIT INFO
 # Provides:             keymap
-# Required-Start:       mountdevsubfs
-# Required-Stop:     
+# Required-Start:       mountdevsubfs $remote_fs
+# Required-Stop:        $remote_fs
 # Default-Start:        S
 # Default-Stop:
 # X-Interactive:       true
---

checkroot.sh declares a Should-Start depndency on keymap which is a
declaration that keymap service should start before checkroot.sh when present,
but now keymap is declaring that it only starts once the $remote_fs virtual
boot checkpoint is satisfied which is much much later in the boot process. This
is an impossible relationship because checkroot.sh is required by other services
which must start before $remote_fs is satisfied.

I would like to know why this change in dependency was made by the
console-common maintainers?

Thanks, Kel.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to