Your message dated Sun, 12 Nov 2006 12:36:25 -0700
with message-id <[EMAIL PROTECTED]>
and subject line fixed in 3.6.3dfsg1-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: systemimager-boot-i386-standard
Version: 3.6.3-2
Severity: grave
Justification: renders package unusable

After setting up partitions, I see:

Load device mapper driver (for LVM).
modprobe: relocation error: modprobe: symbol create_module, version 
GLIBC_2.0 not defined in file libc.so.6 with link time reference
Load addition filesystem drivers.

Then that error is repeated many times.

Then, mke2fs is run to create the ext2 filesystem.  It runs on /dev/hda1 
and appearsto work fine.

Next, it runs:

mkdir -p /a/ || shellout
mount /dev/hda1 /a/ -t ext3 -o defaults || shellout
mount: Mounting /dev/hda1 on /a failed: No such device

I believe this is because of the earlier libc issue.  It failed to load 
the ext3 module into the kernel, therefore it couldn't mount the disk.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-1-xen-amd64
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

systemimager-boot-i386-standard depends on no packages.

Versions of packages systemimager-boot-i386-standard recommends:
ii  systemimager-server           3.6.3-2    Automate GNU/Linux installs and up

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 3.6.3dfsg1-1

severity 393631 grave
merge 393631 398150
thanks

Already fixed in 3.6.3dfsg1-1, which entered testing yesterday.

-- 
dann frazier


--- End Message ---

Reply via email to