Your message dated Sat, 30 Oct 2010 17:51:48 +0200
with message-id <20101030155148.ga2...@wavehammer.waldi.eu.org>
and subject line Re: Bug#600875: Acknowledgement (lvm2: 'Should-Start' should 
depend on mdadm-raid and not mdadm)
has caused the Debian Bug report #600875,
regarding lvm2: 'Should-Start' should depend on mdadm-raid and not mdadm
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 ow...@bugs.debian.org
immediately.)


-- 
600875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lvm2
Version: 2.02.39-8
Severity: grave
Tags: squeeze
Justification: renders package unusable

Hi,

Apart from adding the tweak detailed in #568838, an upgrade from lenny to 
squeeze causes dpkg to grumble about:
----
insserv: There is a loop between service checkfs and lvm2 if started
insserv:  loop involving service lvm2 at depth 8
insserv: There is a loop between service checkfs and lvm2 if started
insserv:  loop involving service mdadm at depth 6
insserv:  loop involving service mountall at depth 4
insserv:  loop involving service checkfs at depth 3
insserv:  loop involving service udev at depth 1
insserv: There is a loop between service mountall and checkfs if started
insserv:  loop involving service networking at depth 5
insserv:  loop involving service urandom at depth 13
insserv:  loop involving service portmap at depth 14
insserv: Max recursions depth 99 reached
insserv: Max recursions depth 99 reached
insserv: Max recursions depth 99 reached
insserv: Max recursions depth 99 reached
insserv: Max recursions depth 99 reached
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
----

Others have reported similar things for other packages (hibernate: #554905) and 
the tweak was to replace mdadm with mdadm-raid; which seems to work for me 
although I have no idea if this is the Right Solution(tm).

Marking 'grave' as the #554905 did the same :)

Cheers

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: sparc (sparc64)

Kernel: Linux 2.6.26-2-sparc64-smp (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lvm2 depends on:
ii  libc6                        2.11.2-6    Embedded GNU C Library: Shared lib
ii  libdevmapper1.02.1           2:1.02.27-4 The Linux Kernel Device Mapper use
ii  libreadline5                 5.2-3.1     GNU readline and history libraries
ii  lsb-base                     3.2-23.1    Linux Standard Base 3.2 init scrip

Versions of packages lvm2 recommends:
ii  dmsetup                      2:1.02.27-4 The Linux Kernel Device Mapper use

lvm2 suggests no packages.

-- Configuration Files:
/etc/init.d/lvm2 changed:
SCRIPTNAME=/etc/init.d/lvm2
. /lib/lsb/init-functions
[ -x /sbin/vgchange ] || exit 0
do_start()
{
        modprobe dm-mod 2> /dev/null || :
        /sbin/vgscan --ignorelockingfailure --mknodes || :
        /sbin/vgchange -aly --ignorelockingfailure || return 2
        [ -x /sbin/udevadm ] && udevadm settle 
}
do_stop()
{
        /sbin/vgchange -aln --ignorelockingfailure || return 2
}
case "$1" in
  start)
        log_begin_msg "Setting up LVM Volume Groups"
        do_start
        case "$?" in
                0|1) log_end_msg 0 ;;
                2) log_end_msg 1 ;;
        esac
        ;;
  stop)
        log_begin_msg "Shutting down LVM Volume Groups"
        do_stop
        case "$?" in
                0|1) log_end_msg 0 ;;
                2) log_end_msg 1 ;;
        esac
        ;;
  restart|force-reload)
        ;;
  *)
        echo "Usage: $SCRIPTNAME {start|stop}" >&2
        exit 3
        ;;
esac


-- no debconf information



--- End Message ---
--- Begin Message ---
On Wed, Oct 20, 2010 at 10:11:17PM +0100, Alexander Clouter wrote:
> False alarm, I thought 2.02.39-8 was squeeze...

reportbug should warn you.

> Close this fault report, sorry for wasting your time.

Closing.

Bastian

-- 
We Klingons believe as you do -- the sick should die.  Only the strong
should live.
                -- Kras, "Friday's Child", stardate 3497.2


--- End Message ---

Reply via email to