[Bug 410310] Re: update-manager inconsistent with download size
Launchpad Bug Tracker
410310 at bugs.launchpad.net
Mon Jul 25 16:50:11 UTC 2011
This bug was fixed in the package update-manager - 1:0.152.7
---------------
update-manager (1:0.152.7) oneiric; urgency=low
[ Michael Vogt ]
* merged lp:~mterry/update-manager/813778 to fix crash in
initCache() LP: #813778. Many thanks to Michael Terry
* add jenkins slave setup (config, upstart job), similar to the
server-isotesting (disabled by default)
* DistUpgrade/DistUpgrade.ui:
- add minimal size for the details expander (and let glade
reindent/reformat the entire file along the way)
* merged lp:~evfool/update-manager/stringfixes
[ Robert Roth ]
* Updated translator comment to follow the Ubuntu Units policy
* Display sizes according to the Ubuntu Units Policy (LP: #410310)
* Fix ambiguous text explaining updates to running release (LP: #461780)
* Added label to distinguish candidate version from installed version
(LP: #537942)
* Rename Check all/Uncheck all to Select/Deselect all
-- Michael Vogt <michael.vogt at ubuntu.com> Mon, 25 Jul 2011 18:44:45 +0200
** Changed in: update-manager (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/410310
Title:
update-manager inconsistent with download size
Status in Update Manager:
Confirmed
Status in “update-manager” package in Ubuntu:
Fix Released
Bug description:
Binary package hint: update-manager
There are three places, where the update-manager states the download size of an update:
-For every package itself
-For all packages together
-During download
The first two and the third one differ. (see attachment - the total and the per-package difference has been fixed in the meantime, the difference between update-manager main window and the progress windows still exists)
When doing an update with update-manager some numbers displayed on screen come from update-manager and some from apt.
And now apt is displaying the numbers with decimal kilos (K=1000), and update-manager is displaying the numbers with binary kilos (K=1024). Even if the float problem is solved, this still gives a difference in display of about 4.8% for Megabyte numbers. (see some more details in my comment #9 above and some of the attached pictures).
Before this bug is set to 'Fix Released' I would like to raise the
question if it would make sense to consistently use one and the same
factor for kilo/mega representation throughout all package management
programs. This could be done either by changing humanize_size to
decimal as well, or changing apt/apt-pkg/strutl.cc to binary, or even
by totally eliminating humanize_size and using also the apt
subroutines in update-manager.
To manage notifications about this bug go to:
https://bugs.launchpad.net/update-manager/+bug/410310/+subscriptions
More information about the foundations-bugs
mailing list