You've got good eyes or something, since this seems to always be happening and not being noticed by most people. From the log:
Oct 24 13:40:50 debconf: --> PROGRESS SET 2
Oct 24 13:40:50 debconf: --> PROGRESS INFO base-installer/section/install_base_system
Oct 24 13:40:50 base-installer: info: Execution hook before debootstrap
Oct 24 13:40:50 debconf: --> PROGRESS INFO base-installer/progress/netcfg
Oct 24 13:40:50 base-installer: info: Running /usr/lib/base-installer.d/40netcfg
Oct 24 13:40:50 debconf: --> PROGRESS SET 0
Oct 24 13:40:50 debconf: --> METAGET base-installer/debootstrap/section/downrel
description
So the reset to 0 happens after check_target and get_mirror_info, which
are each currently given one percent of the progress bar. The next bit is
install_base_system, and the problem is that run-debootstrap just advances
the progress bar from 0 to 100, not taking into account anything that has come
before.
Short of adding smarts about the progress bar's previous position to
run-debootstrap, the easiest fix is probably to make the check_target
and get_mirror_info stages both use 0% of the progress bar. They do run very
quickly after all.
[EMAIL PROTECTED]:~/src/d-i/packages/base-installer/debian>svn diff
Index: postinst
===================================================================
--- postinst (revision 23387)
+++ postinst (working copy)
@@ -833,8 +833,8 @@
NUM_STEPS=$(($NUM_STEPS + $1)) || true
}
-waypoint 1 check_target
-waypoint 1 get_mirror_info
+waypoint 0 check_target
+waypoint 0 get_mirror_info
waypoint 100 install_base_system
waypoint 1 configure_apt
waypoint 3 apt_update
I haven't yet tested this patch, and it may wait until after the release.
--
see shy jo
signature.asc
Description: Digital signature
