On Wed, 11 Oct 2006, Jan De Luyck wrote:
> Package: base-files
> Version: 3.1.16
> Severity: normal
>
>
> Since the last upgrade of base-files I've been having trouble with
> name resolving. After a while I figured it out: when removing the
> mDNS entries in /etc/nsswitch.conf, everything works perfectly.
This issue was fixed in February this year:
base-files (3.1.10) unstable; urgency=medium
* Removed mdns item from hosts line in default /etc/nsswitch.conf, since
it does not make everybody happy (Bugs #348578, #348580 and #351990).
-- Santiago Vila <[EMAIL PROTECTED]> Thu, 9 Feb 2006 18:41:22 +0100
One month later, the way /etc/nsswitch.conf is handled was changed:
base-files (3.1.11) unstable; urgency=low
* The file /etc/nsswitch.conf is now created by postinst in the first
install (made by debootstrap), and it's no longer a conffile.
-- Santiago Vila <[EMAIL PROTECTED]> Sat, 4 Mar 2006 13:26:14 +0100
If you didn't upgrade your system in a month (i.e. you skipped base-files
version 3.1.10), then your system may still have the "bad" default.
I would expect a user of unstable to upgrade the system more than once
a month, and if it's not the case, I would expect him/her to be able
to fix things like this by hand.
> I can easily reproduce this in my Debian SID chroot.
I bet you can't reproduce this on a newly created etch chroot, or in
a newly created sid chroot, and of course, it will not happen when
upgrading from sarge to etch or upgrading from etch to sid.
May I close this bug?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
