[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#473364: installation-report: some install glitches (grub2, tasksel, serial mouse)

reassign 473364 win32-loader
retitle 473364 Should not preseed legacy encodings
severity 473364 important

(Omitting issues previously answered.)

On Friday 04 April 2008, Paul Wise wrote:
> There are some other minor issues below though:
> goodbye-microsoft.com
> wait for grub2 (seems slower than grub1)

Yes, I've seen that too in Virtualbox. It takes a huge amount of time and 
you can actually see the display being "assembled".
/me needs to file a BR about that.

> choose en_AU as an additional language - seems that en_AU.iso88591 got
> preseeded from debian.exe?

If that is true, it would IMO be a pretty serious bug in win32-loader as 
Debian is supposed to be installed using UTF-8 locales by default.

Robert: can you please look into this?

> add ntfs modules component (mouse config seems absent)

Not really needed; will be loaded automatically if needed.

> default kernel (linux-image-2.6-k7 - isn't k7 depreciated or a dummy
> package?)

As long as it exists, I see no harm to continue to select it. When it is 
removed from the archive, D-I will automatically fall back correctly.

> notice windows is at the bottom and that it uses 
> (hd0,0) instead of (hd0,1) boot debian

That's #473401.

> get to nice blue grub2 splash - shouldn't the bootloader and d-i use
> consistent themes?
> gdm comes up - again theme consistency would be good
> again the blue theme, perhaps d-i needs changing to use blue instead of
> red?

See http://lists.debian.org/debian-boot/2008/04/msg00570.html.

> notice some dummy/transitional packages installed
> -> mailx and netcat are not marked as autoinstalled, I guess tasksel
> installed those?

Yes, the transitional packages have a priority of standard or higher, so 
they get installed. Please take this up with the respective maintainers.

Reassigning to win32-loader as that is the only real issue remaining.
Thanks for the elaborate report, though some clearer indication of what you 
consider to be issues would be welcome next time.


Reply to: