Software updater stops complete update if only one source cannot be found

[Daniel erbe]

= WORKAROUND =

For distribution ugprades one can use 'do-release-upgrade -d' instead of 'update-manager -d' to avoid this bug on Quantal.

First bug report so any advice would be appreciated.

Installed 12.10 with no worries and installed a bit of software and added the redshift repo (https://launchpad.net/~jonls/+archive/redshift-ppa). When i next tried to update my system with software updater (1:0.172) stopped with the error

"Failed to download repository information"
 and
"W:Failed to fetch http://ppa.launchpad.net/jonls/redshift-ppa/ubuntu/dists/quantal/main/source/Sources 404 Not Found
, W:Failed to fetch http://ppa.launchpad.net/jonls/redshift-ppa/ubuntu/dists/quantal/main/binary-amd64/Packages 404 Not Found
, W:Failed to fetch http://ppa.launchpad.net/jonls/redshift-ppa/ubuntu/dists/quantal/main/binary-i386/Packages 404 Not Found
, E:Some index files failed to download. They have been ignored, or old ones used instead.".

I fixed this by unchecking the redshift PPA in software sources.
I am sure update-manager used to continue updating all other packages while leaving the one that the source could not be found for, rather than not updating anything in the system including security because of one insignificant package?

ProblemType: BugDistroRelease: Ubuntu 12.10
Package: update-manager 1:0.170
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
Date: Tue Sep 11 18:11:17 2012
GsettingsChanges:
 b'com.ubuntu.update-manager' b'first-run' b'false'
 b'com.ubuntu.update-manager' b'launch-time' b'1347357820'
 b'com.ubuntu.update-manager' b'show-details' b'true'
 b'com.ubuntu.update-manager' b'window-height' b'901'
 b'com.ubuntu.update-manager' b'window-width' b'569'
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120903.4)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bashSourcePackage: update-manager
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Marco Trevisan (Treviño) (3v1n0)]

Confirming here... I think this is a quite important bug. If the download of a non-official source fails, it should not be enough to stop the whole update process.

[Matthew Paul Thomas (mpt)]

Similar:
* bug 926021 -- no updates are installed because one couldn't be downloaded
* bug 978315 -- no updates are installed because one PPA wasn't authenticated.

[Matthew Paul Thomas (mpt)]

Spec update coming soon, but here's what I have so far:

In all cases when this error occurs, the alert should have the secondary text, "Some software couldn’t be checked for updates. Open the Settings for more information."

And on a manual launch with no other sources offering updates, the primary text should not be the usual "The software on this computer is up to date." It should instead be the less definite "No software updates are available.", or something close to that.

When you do click Settings, it should scroll to and pre-select the first 404ing source in the list of sources. And all 404ing sources should have a /!\ icon or similar.

[Michael Terry (mterry)]

I've got a branch proposed for merging, but it does *not* do the Settings bits yet (we don't have granularity right now about which specific sources had problems). Because of that, I've dropped the "Open the Settings for more information" sentence until that gets implemented.

[Matthew (mh00h)]

This bug has not been fixed running an Ubuntu 12.10 machine with multiple repositories not found. Also, running "update-manager -d" is not possible until this bug is fixed. Does anyone know if this will prevent people who have bad repro's from updating to 13.04 once deployed?

[Brian Murray (brian-murray)]

This was not referenced in a changelog but has been fixed in Raring.

[Brian Murray (brian-murray)]

@Matthew - See my change to the description for a workaround for upgrading from Quantal to Raring. Having a PPA enabled will not necessarily prevent you from upgrading to Raring, however they will be disabled during and after the upgrade process.

[Michael Terry (mterry)]

Is this SRU material? It's a semi-invasive patch, adds new strings, and has a workaround (disable PPAs that don't work anymore).

[Rolf Leggewie (r0lf)]

quantal has seen the end of its life and is no longer receiving any updates. Marking the quantal task for this ticket as "Won't Fix".

[inaki31 (inakimiceram)]

Some index files failed to download. They have been ignored, or old ones used instead.