Missing python2.4 dependencies after running dist-upgrade on hoary

Bug #11395 reported by Dag Rune Sneeggen
8
Affects Status Importance Assigned to Milestone
gimp (Ubuntu)
Fix Released
Medium
Jan Groenewald

Bug Description

With a fresh Ubuntu 4.10 warty CD Image, I tried to follow the procedures at
http://www.ubuntulinux.org/wiki/GuideToHoary.
Before doing so, I ran dist-upgrade with the following sources.list file:
http://www.dudcore.net/sources.list.warty
Unfortunantly, I cannot obtain a list of installed packages at this time, as I
suppose that list isn't available after I did my next move.
After changing my sources.list to this:
http://www.dudcore.net/sources.list.hoary, I ran dist-upgrade once again. This
was just a few hours ago.
This resulted in the following: http://www.dudcore.net/apt-get_22-12-04.log
(Sorry about the norwegian locale, but this is actually my 12 year old sister's
computer... But the syntax should be familiar for anyone adept at apt-get.)

I've (afterwards) tried downloading the package listed in the URL section of
this bug, and using dpkg --force-all -i <package_name> to get it working, but it
still gives the exact same error messages.

http://ftp.belnet.be/linux/ubuntu/pool/main/p/python2.4/python2.4_2.4-2ubuntu1_i386.deb: http://ftp.belnet.be/linux/ubuntu/pool/main/p/python2.4/python2.4_2.4-2ubuntu1_i386.deb

Revision history for this message
Colin Watson (cjwatson) wrote :

Doesn't look like you're fully upgraded yet. Most of the packages listed there
no longer depend on python (<< 2.4) in hoary.

Try 'apt-get dist-upgrade' again, and post the log.

Revision history for this message
Dag Rune Sneeggen (contactus) wrote :

Hi there Colin, thank you for the swift reply :)

Here's a log of dist-upgrade today http://dudcore.net/apt-get_23-12-04.log.
Please advise further...

Cheers and happy christmas from a Norwegian christmas nisse. ;D

Revision history for this message
Colin Watson (cjwatson) wrote :

OK, thanks. What happens if you run 'apt-get -f install', as suggested at the
start of the output?

A better apt frontend like aptitude or synaptic may also be better at dealing
with this.

Revision history for this message
Dag Rune Sneeggen (contactus) wrote :

Oh, that did the trick.
I originally tried 'apt-get -d install <package_name>'
Wasn't aware that you could actually run just 'apt-get -f install'.
Thanks for fixing the bug. That made it install/upgrade more than 100 packages.
Although right afterwards I ran 'apt-get dist-upgrade' again, it went a head and
downloaded close more than 100 packages, mostly the same as before, and
installed them all just fine.
I realize this wasn't an "error" per say. But it is unintentional behaviour. Bad
dependencies on upgrading a fresh install, according to information in the
official wiki. Something should be fixed shouldn't it? That is, if more folks
than me experienced it...

...Anyone? Hehe....

Cheers!
(In reply to comment #3)
> OK, thanks. What happens if you run 'apt-get -f install', as suggested at the
> start of the output?
>
> A better apt frontend like aptitude or synaptic may also be better at dealing
> with this.

Revision history for this message
Matt Zimmerman (mdz) wrote :

This was part of the normal transition process to python 2.4; things like this
happen when you run a development release.

Anyway, it was fixed some time ago.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.