Your message dated Thu, 18 Jul 2013 11:48:53 +0200
with message-id <[email protected]>
and subject line dealing with old installation-reports and d-i related bugs
has caused the Debian Bug report #601475,
regarding debian-installer: Graphical installer silently fails network dev
config
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
601475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601475
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debian-installer
Version: Beta 1
Severity: normal
Using the Squeeze Beta 1 installer in graphical mode on a Compaq DL380 G2,
udhcpc fails. There's no clue what the fail is.
What's needed is the firmware-linux-nonfree package so Intel 82559 D101M
microcode (e100/d101m_ucode.bin) is available.
A recent install on a Thinkpad T400 hinted that a firmware package was needed
for the wireless network device.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
reassign 545987 partman-newworld
reassign 524342 grub-pc
reassign 560348 xen-utils-common
reassign 596667 netcfg
thanks
Hi,
thank you for submitting installation reports, much appreciated.
I read through all the bugs mentioned here (and I'm sure they were read by
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they have been from a development phase where things were not stable and/or
- they are (very) old, between 2.5 and >4 years (so thats 2 releases ago).
If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll
do if requested) or just file a new one - thats often better, as the bug log
will be clearer and shorter and not contain cruft.
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
--- End Message ---