Bug#351244: installation-reports: AMD64 install fails after package selection w/ termwrap not found
Frans Pop wrote:
>On Friday 03 February 2006 14:54, cmetzler@speakeasy.net wrote:
>
>> 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?
Sorry I was vague. I do indeed mean that this occurred after removing
the netinstall CD and rebooting my own system, and continuing with the
rest of the install (root pwd, creating a user, initial package selection
through tasksel, etc.). It occurred after package downloading and
configuration questions were done. However, to begin the installation,
I definitely used a daily build netinstall image, downloaded from
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
on 2006-01-11.
> FYI: I tested an installation using current daily AMD64 netboot image
> (installing testing) and had no problems.
I've downloaded the same and am about to try it.
Thanks much,
-c
Reply to: