update-manager can't handle sources.list containing deb [arch=$arch] style lines

[Steve Langasek]

Binary package hint: update-manager

On a maverick system which has sources.list entries like this enabled for multiarch testing,

deb [arch=amd64] http://us.archive.ubuntu.com/ubuntu/ maverick main restricted

update-manager -d spits out a scary warning message that it can't find a valid mirror:

  No valid mirror found

  While scanning your repository information no mirror entry for the upgrade was found. This can happen if you run a internal mirror or if the mirror information is out of date.

  Do you want to rewrite your 'sources.list' file anyway? If you choose 'Yes' here it will update all 'maverick' to 'natty' entries.
If you select 'No' the upgrade will cancel.

Removing the [arch] annotations is sufficient to make update-manager happy. (Actually, update-manager removes them on its own, even if you click 'no' here, because it manages to update sources.list before throwing this error...)

I guess we'll want update-manager to handle multiarch sources.list entries better for natty->oneiric upgrades.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: update-manager 1:0.142.22
ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic x86_64
Architecture: amd64
Date: Thu Mar 24 14:50:43 2011
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: update-manager

[RedSingularity (redsingularity)]

Does this occur right after initiating "update-manager -d", or do you hit the "Check"/"Install Updates" first and then get the error?

[Steve Langasek (vorlon)]

I don't recall, but that hardly seems like information that's material to trying to fix the bug if you try to reproduce it or are familiar with the code. Setting back to new.

[Steve Langasek (vorlon)]

Correction, I do recall. It's only when you click the "upgrade" button.

[RedSingularity (redsingularity)]

Ok thanks. I was asking because simply running the command "update-manager -d" was not bringing up the error. I am trying to reproduce it again.

[RedSingularity (redsingularity)]

I can confirm this on my machine as well. The WARNING will be in the terminal window after clicking "Upgrade" in the update-manager. I will talk to someone about marking this "Triaged" right away. Thanks for reporting it.