I wonder why such a serious bug hasn't been fixed yet. I had to reinstall a Debian machine unexpectedly and being confronted with this bug in the rush was no pleasant experience. I wasted a significant amount of time finding out what was the hidden thing rendering my newly installed system into an unusable state. If it at least put a comment line to resolv.conf informing about the source of its modification, I could simply remove the package immediately and be done with the problem (it would still be a bug, but much less annoying one).
Silently overwriting an important system file without being asked to do so and without any explanatory notice is not acceptable. Please either fix the bug or make sure the package is not installed by default. Thank you, Milan
