Failed to update to jaunty via update-manager

[Victor Costan]

Binary package hint: update-manager-core

I am on Ubuntu 8.10 and trying to update to the 9.04 alpha, by running "sudo update-manager -d". I get the following error

W:Failed to fetch http://security.ubuntu.com/ubuntu/dists/jaunty-security/Release Unable to find expected entry partner/binary-i386/Packages in Meta-index file (malformed Release file?)
, W:Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/jaunty-updates/Release Unable to find expected entry partner/binary-i386/Packages in Meta-index file (malformed Release file?)
, E:Some index files failed to download, they have been ignored, or old ones used instead.

Output for apt-cache policy update-manager-core
  Installed: 1:0.93.34
  Candidate: 1:0.93.34
  Version table:
 *** 1:0.93.34 0
        500 http://us.archive.ubuntu.com intrepid-updates/main Packages
        100 /var/lib/dpkg/status
     1:0.93.32 0
        500 http://us.archive.ubuntu.com intrepid/main Packages

I looked in /var/log/dist-upgrade and attached the log file with relevant information.

[Jed Clinger (jed-clinger)]

I had exactly the same problem trying to update 8.10 to 9.04 alpha with "update-manager -d"

[Melik Manukyan (djmelik)]

I had a similar problem as well.

1) Go to System > Administration > Software Sources.
2) Scroll to the "Third-Party Software" tab.
3) Uncheck the intrepid related repositories.

Then attempt to update to jaunty again.

[Matt Zimmerman (mdz)]

Confirmed here as well. I'll attach my sources.list before and after the upgrade step

[Matt Zimmerman (mdz)]

The problem appears to be in the handling of the partner repository:

 # active distribution
-deb http://archive.ubuntu.com/ubuntu/ intrepid main restricted universe multiverse
-deb http://archive.canonical.com/ intrepid partner
-deb http://archive.ubuntu.com/ubuntu/ intrepid-updates main restricted universe multiverse
-deb http://archive.ubuntu.com/ubuntu/ intrepid-proposed main restricted universe multiverse
-deb http://security.ubuntu.com/ubuntu/ intrepid-security main restricted universe multiverse
+deb http://archive.ubuntu.com/ubuntu/ jaunty main restricted universe multiverse
+deb http://archive.canonical.com/ jaunty partner
+deb http://archive.ubuntu.com/ubuntu/ jaunty-updates main restricted universe multiverse partner
+deb http://archive.ubuntu.com/ubuntu/ jaunty-proposed main restricted universe multiverse
+deb http://security.ubuntu.com/ubuntu/ jaunty-security main restricted universe multiverse partner

Note that partner only exists on archive.canonical.com, but it's been added to the archive.ubuntu.com line. Commenting out the partner line above doesn't avoid the problem though.

[Matt Zimmerman (mdz)]

2009-01-15 12:01:13,746 INFO fixing components inconsistency from 'deb http://archive.ubuntu.com/ubuntu/ jaunty-updates main restricted universe multiverse'
2009-01-15 12:01:13,746 INFO to new entry 'deb http://archive.ubuntu.com/ubuntu/ jaunty-updates main restricted universe multiverse partner'
2009-01-15 12:01:13,746 INFO fixing components inconsistency from 'deb http://security.ubuntu.com/ubuntu/ jaunty-security main restricted universe multiverse'
2009-01-15 12:01:13,746 INFO to new entry 'deb http://security.ubuntu.com/ubuntu/ jaunty-security main restricted universe multiverse partner'

[Launchpad Janitor (janitor)]

This bug was fixed in the package update-manager - 1:0.96.3

---------------
update-manager (1:0.96.3) jaunty; urgency=low

  * DistUpgrade/DistUpgradeController.py:
    - when syncing inconsitent components, only sync those
      we know about (LP: #312092)
  * tests/test_sources_list.py:
    - add regression test for #312092

 -- Michael Vogt <email address hidden> Thu, 15 Jan 2009 14:14:01 +0100

[Matt Zimmerman (mdz)]

Verified, thank you, the upgrade is now able to continue past this step. Fingers crossed for the rest. :-)

[Michael Vogt (mvo)]

Thanks Matt :) I did some successful test upgrades in my virtual machine setup, fingers crossed for your setup.