Your message dated Sun, 25 Aug 2013 10:18:09 +0200 with message-id <201308251018.25686.hol...@layer-acht.org> and subject line dealing with old debian-installer bugs has caused the Debian Bug report #602167, regarding debian-installer: resolv.conf either wrongly updated or never written properly (missing nameserver entry) 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 ow...@bugs.debian.org immediately.) -- 602167: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: debian-installer Version: squeeze beta1 kFreeBSD Severity: important When using the expert installer, it seems that /etc/resolv.conf gets updated with the search line, but there is no "nameserver" line. In my case it should pull this information either from DHCP (but it still asked me for it), but even after entering the IP address of the nameserver, it was still missing. This lead to me being unable to select any networked mirror. Adding "nameserver 1.2.3.4" to /etc/resolv.conf under /target solved this problem. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 8.1-1-amd64 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---reassign 421338 debian-cd retitle 421338 ia64 CDs should warn that they are not amd64 thanks Hi, thank you for submitting bug reports concering debian-installer, 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 and/or - they are wishlist but rather special + exotic and not have been acted on for years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to close wishlist bugs.) 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 - and that's often better, as the bug log will be clearer and shorter and not contain cruft. cheers, Holgersignature.asc
Description: This is a digitally signed message part.
--- End Message ---