More Fun with Unmet Dependencies

[John Lyon]

I thought the situation was resolved yesterday, but today, booting up the
box, I'm back where I started, although I know that the OS has been
successfully installed:

-  Power on the box (PowerPC G3, OldWorld Mac)

-  Boots, and loads KDE, and I login.

-  Before it gets the desktop fully loaded (and Toolbar or menu bar, however
it's known in the KDE world), it kills KDE, and returns to the text based
Ubuntu Configuration. It tells me it's "Installing Packages."

At 5% it fails. Over on the 4th console, it shows:

The following packages have unmet dependencies
Libesd-alsa0: conflicts: libesd0 but 0.2.36.1ubuntu5 is to be installed.

I've gone through apt-get -f upgrage and apt-get -f install, to no avail.

I tried swearing at it with the strongest curse words I know, some even in
French.

My concern, aside from getting beyond this show stopper, is that any time I
install or remove some package, that I'll end up with a system that isn't
useful because of these dependencies. I thought the package managers were
supposed to, you know, manage dependencies?

Is there something I'm missing, or something stupid I'm doing? I'm always
ready to admit to my own stupidity.

-- 
John Lyon
Austin TX