Upgrade to edgy: can't resolve courier packages dependency

[NoOp]

On 04/07/2007 09:00 PM, marc wrote:

> 
> The network is operational; it's DNS that is borked. I've no idea what
> edgy does, but it appears to install a local DNS server - I didn't ask
> for it, nor do I want it - and because that's failed, then there is no
> DNS on the machine. This was a fully operational, problem-free machine
> before attempting the upgrade.
> 

What do you show in /etc/resolv.conf? This file should have your dns
servers listed. Are you dhcp or static?

I would change all of your http://archive.ubuntu.com references to
http://uk.archive.ubuntu.com - I have noticed significant problems with
the default http://archive.ubuntu.com recently.

For examples see:
http://www.google.com/search?hl=en&q=91.189.89.6&btnG=Google+Search

I would also try the following from a terminal window if you actually
think that dns is not working properly:

$host google.com

that should return something similar to:
google.com has address 72.14.207.99
google.com has address 64.233.167.99
google.com has address 64.233.187.99
google.com mail is handled by 10 smtp4.google.com.
google.com mail is handled by 10 smtp1.google.com.
google.com mail is handled by 10 smtp2.google.com.
google.com mail is handled by 10 smtp3.google.com.

If it does not, then you may indeed have a dns problem. If so then try:

$sudo dhclient

You can also try /etc/init.d/networking restart but I've found that
dhclient seems to work better, even with a static IP assignment, in
situations like this.