Bug#399316: postinst breaks

[Santiago Garcia Mantinan]

Package: mdadm
Version: 2.5.6-5
Severity: serious

I don't have much info on this one and also the description is not good, but
that's all I saw, I upgraded to latest unstable version and postinst fails,
going back to the version in testing works perfectly. I even purged mdadm
so that I didn't have any old posibly corrupt stuff around but that didn't
help either.

This is what happens on configuring the package:

Setting up mdadm (2.5.6-5) ...
-e If your system has its root filesystem on an MD array (RAID), it 
needs to be started early during the boot sequence. If your root 
filesystem is on a logical volume (LVM), which is on MD, all constituent
arrays need to be started.

If you know exactly which arrays are needed to bring up the root 
filesystem, and you want to postpone starting all other arrays to a 
later point in the boot sequence, enter the arrays to start here. 
Alternatively, enter 'all' to simply start all available arrays.

If you do not need or want to start any arrays for the root filesystem, 
leave the answer blank (or enter 'none'). This may be the case if you 
are using kernel autostart or do not need any arrays to boot.


Please enter a space-separated list of devices, 'all', or 'none'. You 
may omit the leading '/dev/' and just enter e.g. "md0 md1", or "md/1 
md/d0".: unknown option
debconf: whiptail output to the above errors, giving up!
dpkg: error processing mdadm (--configure):
 subprocess post-installation script returned error exit status 255
Errors were encountered while processing:
 mdadm
E: Sub-process /usr/bin/dpkg returned an error code (1)

The above error was when running apt-get upgrade without any LANG on the
environment, I typically have LANG=es_ES at euro and the message I get before
the unknown option is the same one (in english).

I'm currently running one of the 2.6.29 rc versions, but I have tested this
right now with linux-image-2.6.18-1-k7 (booted with this kernel and then
downgraded to testing version and tried to upgrade to unstable again) and it
had the same behaviour.

I believe that the info that follows will give you enough info to know what
I can posibly have around to triger this, if you find something is missing
just ask for it.

Regards!

-- Package-specific info:
--- mount output
/dev/md1 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/md0 on /org type ext3 (rw)
//rut/ on /rut type smbfs (rw)

--- mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=7c5670d2:4f54e411:411e9714:06c414bd
ARRAY /dev/md3 level=raid1 num-devices=2 UUID=1a0e867b:10db3608:1fdec9ed:ef4caaf2
ARRAY /dev/md0 level=raid0 num-devices=2 UUID=4c6bd397:87a82545:da8f260e:16a8eca0

# This file was auto-generated on Thu, 16 Nov 2006 17:55:28 +0100
# by mkconf $Id: mkconf 240 2006-10-26 20:42:03Z madduck $

--- /proc/mdstat:
Personalities : [raid0] [raid1] 
md1 : active raid1 hdd3[0] hda3[1]
      10040512 blocks [2/2] [UU]
      
md3 : active raid1 hdd5[0] hda5[1]
      401472 blocks [2/2] [UU]
      
md0 : active raid0 hdd6[0] hda6[1]
      285265920 blocks 64k chunks
      
unused devices: <none>

--- /proc/partitions:
major minor  #blocks  name

   3     0  156290904 hda
   3     1    3212968 hda1
   3     3   10040625 hda3
   3     4          1 hda4
   3     5     401593 hda5
   3     6  142633071 hda6
  22    64  156290904 hdd
  22    65     722893 hdd1
  22    67   10040625 hdd3
  22    68          1 hdd4
  22    69     401593 hdd5
  22    70  142633071 hdd6
   9     0  285265920 md0
   9     3     401472 md3
   9     1   10040512 md1

--- initrd.img-2.6.19-rc5:

--- /proc/modules:

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.19-rc5
Locale: LANG=es_ES at euro, LC_CTYPE=es_ES at euro (charmap=ISO-8859-15)

Versions of packages mdadm depends on:
ii  debconf [debconf-2.0]        1.5.9       Debian configuration management sy
ii  libc6                        2.3.6.ds1-8 GNU C Library: Shared libraries
ii  lsb-base                     3.1-20      Linux Standard Base 3.1 init scrip
ii  makedev                      2.3.1-83    creates device files in /dev

Versions of packages mdadm recommends:
ii  module-init-tools             3.3-pre3-1 tools for managing Linux kernel mo
ii  postfix [mail-transport-agent 2.3.4-1    A high-performance mail transport 

-- debconf information:
* mdadm/autostart: true
* mdadm/mail_to: root
  mdadm/initrdstart_msg_errmd:
  mdadm/initrdstart: /dev/md1
  mdadm/initrdstart_msg_errconf:
  mdadm/initrdstart_notinconf: false
  mdadm/initrdstart_msg_errexist:
  mdadm/initrdstart_msg_intro:
* mdadm/autocheck: true
  mdadm/initrdstart_msg_errblock:
* mdadm/start_daemon: true