Upgrade to edgy: can't resolve courier packages dependency

[Mario Vukelic]

On Sat, 2007-04-07 at 02:58 +0100, marc wrote:
> No, I don't. I remember seeing a similar message on one of my Debian
> boxes a year or so back, but never on the dapper box in question.

Possibly just a temporary authentication problem of the mirror. To make
authentication effective, one should not install anything while the
message comes up (otherwise, why bother with authentication at all).


>  FYI, I do have a few non-apt packages knocking about. For example: pan 
> and Firefox2, and a backport of vim7 - although I think pan and vim7 
> have been "absorbed" into edgy as part of the upgrade.

"Absorbed" sounds scary. You should either install to /usr/local if you
install from source, or, better yet, use "checkinstall" to create an
easily removable deb package from the sources. 
But this untidiness should have nothing to do with the current
problem :)

> results of "apt-cache policy courier-authlib" and the same for courier-authdaemon.

That looks ok

> > Also, what happens if you do sudo "sudo aptitude dist-upgrade" instead
> > of "sudo aptitude upgrade"?

Since there are 150 packages to be upgraded, and aptitude's
recommendation is reasonable, I would continue with this, if possible in
your current situation (no update possible). Then continue with
alternating "apt-get -f install" and "aptitude dist-upgrade" until,
hopefully, it sorts itself out. Also make sure that these packages are
installed:
ubuntu-minimal
ubuntu-standard 
ubuntu-desktop or kubuntu-desktop or xubuntu-desktop

> > And please post your /etc/apt/sources.list
> 
> # Ubuntu supported packages (packages, GPG key: 437D05B5)
> deb http://archive.ubuntu.com/ubuntu/ edgy main restricted universe 
> multiverse
> deb http://gb.archive.ubuntu.com/ubuntu/ edgy-updates main restricted 
> universe multiverse

I note that the regular repository is a different mirror from the update
repository. This might sometimes cause problems if the mirrors are out
of sync. I would change the first one to
http://gb.archive.ubuntu.com/ubuntu/ too, if you are in GB
      ^^^

> Note that I can't currently do an aptitude update because DNS is 
> inoperative.

This is bad since packages might need to be fetched from the network.
Also, your dependency problems might possibly stem from the fact that
apt's package info is not fully up to date. It would certainly help if
you could get then network operational.