This bug was fixed in the package update-manager - 1:0.87.1
---
update-manager (1:0.87.1) hardy; urgency=low
* UpdateManager/UpdateManager.py:
- fix crash if /var/lib/apt/periodic/update-stamp does not exists
(LP: #181390)
- fix misleading string when cache is rebuild
** Changed in: update-manager (Ubuntu)
Importance: High => Undecided
Assignee: Michael Vogt (mvo) => (unassigned)
Status: Confirmed => Fix Committed
Target: hardy-alpha-4 => None
** Changed in: update-manager (Ubuntu)
Importance: Undecided => High
Assignee: (unassigne
It turns out the reason for this is that those packages are newer in
gutsy than in harder, e.g. firefox:
hardy 2.0.0.10+2nobinonly-0ubuntu2
gutsy 2.0.0.6+2nobinonly-0ubuntu1
security2.0.0.11+2nobinonly-0ubuntu0.7.10
updates 2.0.0.11+2nobinonly-0ubuntu0.
Thanks for your bugreport.
I can confirm this behavior in a test-environment. For some reason those
packages get marked as "obsolete".
Thanks,
Michael
** Changed in: update-manager (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Michael Vogt (mvo)
Status: New =>