Comment 4 for bug 520601

Revision history for this message
Praxis (ebiow) wrote :

I did a distro upgrade from karmic to lucid without using the upgrade manager. I just replaced karmic with lucid in my sources.list, updated, and did a apt-get dist-upgrade. So medibuntu, partner, backports, updates, restricted & multiverse were enabled during the upgrade as well. I did this because I already had the debs on my local server using approx and didn't want to have to download them again.

Two packages hung up, autofs/autofs5 & libanyevent-perl. I removed those and a a couple of programs that depended upon them with 'apt-get remove' and the dist-upgrade continued. Or at least the machine thrashed around and installed a bunch of programs. I had to continue with 'apt-get dist-upgrade' after both rounds of program removals and subsequent upgrades. When I finished upgrading I rebooted but couldn't log in to KDE, I was bounced back to the KDM. So I'm now using Gnome, but I got a warning that that I didn't have autofs and libanyevent, so I sent the automated bug report (I believe) and was escorted to this page. Now that I'm back in the GUI I successfully installed autofs and libanyevent-perl, so I'll try KDE again.

 BTW, I updated another machine with a similar process a couple of days ago and had a similar experience, again, those two packages required manual removal for the upgrade to lucid to go throw. Perhaps I'm just having these issues because I have so many extraneous repositories enabled during my upgrade.