Your message dated Fri, 23 Mar 2007 23:43:06 -0400
with message-id <[EMAIL PROTECTED]>
and subject line #345276
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: debian-installer
Severity: minor
during stage 2, the installer runs an "apt-get update", then "apt-get
install mdetect" in rapid succession. some ftp servers, such as
ftp.debian.org, detect this as hammering and block connectivity for
something like 2 minutes. an error message about unable to connect
to server is presented, which is potentially disconcerting to the
user. if not patient, he or she may give up on the install
even though everything is working fine.
this was discovered using the sarge 3.1r0a netinst d-i CD
(http://cdimage.debian.org/debian-cd/3.1_r0a/i386/iso-cd/debian-31r0a-i386-netinst.iso).
to reproduce, choose ftp.debian.org as an ftp apt source during stage 2.
i'm not sure if this affects the etch beta 1 installer as well.
i did a comprehensive search of the d-i bug reports, but didn't see
anything that addressed this issue yet.
thanks for the hard work. hope you all have a happy new year.
mike
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (600, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
--- End Message ---
--- Begin Message ---
i had seen this problem originally with sarge when it was in testing.
however, i have not observed this behavior with any of the etch d-i
installation images during the entire etch testing time frame, so i am
convinced that this is no longer a bug.
thanks for the hard work.
--- End Message ---
