Bug 504828 - The amount of space that is needed for system updates is calculated incorrectly
Summary: The amount of space that is needed for system updates is calculated incorrectly
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-packagekit
Version: 11
Hardware: i386
OS: Linux
low
high
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-09 16:58 UTC by Stan Salatov
Modified: 2014-01-21 23:09 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-20 15:43:47 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
before and after -- note space calculation (113.80 KB, image/png)
2009-06-09 16:58 UTC, Stan Salatov 		no flags Details
View All

Description Stan Salatov 2009-06-09 16:58:09 UTC 
Created attachment 347057 [details]
before and after -- note space calculation

Description of problem: The amount of space that is needed for system updates is calculated incorrectly.


Version-Release number of selected component (if applicable): 
gpk-update-viewer 2.27.2


How reproducible: occurs every time.


Steps to Reproduce:
1. Open "Software Updates"
2. Check the box to install a package
3. Uncheck the box.
  
Actual results:
The estimated space that's needed to install the packages always increases. Not only that, it also increases in megabytes, even though the package that's being selected is only 9k. (screenshot attached).

Expected results:
As you check or uncheck the selection boxes, the calculations must be performed correctly.

Additional info:
Comment 1 James Antill 2009-06-09 17:07:53 UTC 
No idea, I assume gpk is doing something weird.
Comment 2 Richard Hughes 2009-06-09 19:14:25 UTC 
Should be fixed here: https://admin.fedoraproject.org/updates/F11/FEDORA-2009-5748 -- please confirm.
Comment 3 Stan Salatov 2009-06-09 21:56:55 UTC 
Yep, it works fine now!! Thanks.
Note You need to log in before you can comment on or make changes to this bug.