updates-available is inaccurate
Bug #427373 reported by
Dustin Kirkland
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
byobu (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: byobu
Byobu's updates_available is inaccurate, particularly immediately following an apt install or update. Previously we were relying on update-notifier, but the api has changed there.
We should fix byobu's updates_available mechanism to be more accurate to the present state of the system, and avoid unnecessary work. We can look at the timestamp on /var/lib/apt, and trigger background updates (writing those cache) only when /var/lib/apt is newer than our cache file.
:-Dustin
Changed in byobu (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → Medium |
summary: |
- updates-available should use update-notifier-common + updates-available is inaccurate |
description: | updated |
To post a comment you must log in.
This bug was fixed in the package byobu - 2.31-0ubuntu1
---------------
byobu (2.31-0ubuntu1) karmic; urgency=low
[ Dustin Kirkland ] available, profiles/common:
* bin/updates-
- reworked to be far more efficient, and accurate, LP: #427373
- look at the timestamp on /var/lib/apt, and only update cache
if /var/lib/apt has been touched since the cache
- in particular, these changes fix a bug when the user does an
apt-get install or upgrade, and changes to the update status
are not update for up to an hour later; with these fixes, it's
nearly immediate
- and now that updates_available is trivial (in most cases), we
can run it more frequently
[ Mathias Gug ]
* Check that byobu-launcher exists before calling it (chroots use the same
.profile as the main system but may not have byobu installed).
-- Dustin Kirkland <email address hidden> Mon, 31 Aug 2009 19:30:20 -0500