update-manager cancels entire update because of one ppa
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
I just tried doing an update via update-manager. It said there were 435 updated packages for my Precise system.
However, update-manager refused to update anything because of one unauthenticated PPA.
I have the following PPA info in my sources.list file for Audacity.
etc/apt/
/etc/apt/
/etc/apt/
/etc/apt/
And because of that single PPA, update-manager refuses to update ANYTHING on my precise system. This has been a problem for longer than precise. If I update via console using apt-get dist-upgrade, apt-get gives me the option to accept that the PPA is not authenticated, and then proceeds to update my system.
Since Update Manager is the way users are expected to update their systems, having it refuse to update anything because of one PPA package is really bad. It should either match the behaviour of apt-get, or it should simply skip that package and provide a message at the end saying "Package X was not updated because of reason Y"
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: update-manager 1:0.156.10
ProcVersionSign
Uname: Linux 3.2.0-21-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0-0ubuntu2
Architecture: amd64
Date: Tue Apr 10 15:50:39 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120307)
PackageArchitec
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: update-manager
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in update-manager (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #926021, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.