Your message dated Wed, 06 Sep 2006 09:35:27 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#386019: vmlinux/vmlinuz confusion
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: kernel-image-2.4.27-xxs1500
Version: 2.4.27-10.sarge3.040815-1
Severity: Important
During the installation of debian/mipsel using the gxemul emulator
(simulating a DECstation 5000/200, see more at [1] or [2]),
the installation of the base system fails near to the end while
installing package kernel-image-2.4.27-xxs1500. At closer inspection,
it seems that this package installs a /boot/vmlinux-2.4.27-xxs1500
(mind the "x" in vmlinux) while some post-inst scripts expects a
/boot/vmlinuz-2.4.27-xxs1500 (mind the "z"). Exact message of the
failed dpkg is:
Setting up kernel-image-2.4.27-xxs1500 (2.4.27-10.sarge3.040815-1) ...
Internal Error: Could not find image (/boot/vmlinuz-2.4.27-xxs1500)
I would rate this problem as "Important" since it prevents to
continue with the rest of the installation, except if you are clever
enough to try again after placing the right symlink in /boot
manually.
Unfortunatelly, I've no way of telling wether etch is affected by the
same bug (Can't boot d-i with this emulator...).
By the way, should the debian-installer team be warned of the issue ?
(and how ?)
Best regards,
Pierre Letouzey
[1] http://gavare.se/gxemul/gxemul-stable/doc/guestoses.html#declinux
[2] http://www.pps.jussieu.fr/~letouzey/emul_debianmips.en.html
--- End Message ---
--- Begin Message ---
Version: 10.011
Hi,
Ah. This was fixed a while ago;
2005-10-23 Manoj Srivastava <[EMAIL PROTECTED]>
* rules (kimagesrc):
[EMAIL PROTECTED]/kernel-package--devel--9.0--patch-42
Well, calling kimage vmlinux.srec was breaking the
postinst. However, kimage does not seem to be used
anywhere except in determining the next value, namely,
kimagesrc -- so I just added .srec to kimagesrc, and
thus eliminated the need for hacking the postinst.
That made it into unstable in version 10.011 on 2005-12-01
done
--
You are magnetic in your bearing.
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.datasync.com/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--- End Message ---
