Bug#351244: installation-reports: AMD64 install fails after package selection w/ termwrap not found
On Friday 03 February 2006 14:54, cmetzler@speakeasy.net wrote:
> Comments/Problems:
> The problem ended
> up being that when menu.lst was written and Grub was installed,
> the SATA drive (on which the operating system was installed)
> was identified as (hd3) (the three IDE drives got (hd0) through
> (hd2)), so the "root" line in Grub's menu.lst identified the
> root partition as (hd3,0).
This is a known issue that we hope to resolve after the Beta2 release for
the installer.
> Problem #2 was a showstopper: during the second half of the install,
> after using what looks like the current incarnation of tasksel to pick
> stuff to install, I got configuration questions about those packages
> (e.g. exim configuration stuff). Then, at the point where it'd
> presumably start installing and configuring all the packages it had
> fetched, my screen flooded with a zillion instances of:
What exactly do you mean by "the second half of the install"?
Do you mean the base-config run after the reboot? In that case you were
_not_ using a snapshot (or daily build) of the installer, but the Etch
Beta2 release...
The problem you saw could then be explained by the fact that some packages
accidentally migrated to testing yesterday. This is documented on:
http://wiki.debian.org/DebianInstallerToday.
It says there that the netinst image is OK, but I guess it could break if
base-config is upgraded during the tasksel run after the reboot.
Can you confirm that this is what happened?
FYI: I tested an installation using current daily AMD64 netboot image
(installing testing) and had no problems.
Cheers,
FJP
Reply to: