Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 134877 - up2date GUI shows "0 kB" in size column
Summary: up2date GUI shows "0 kB" in size column
Keywords:
Status: CLOSED DUPLICATE of bug 107048
Alias: None
Product: Fedora
Classification: Fedora
Component: up2date
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bret McMillan
QA Contact:
URL:
Whiteboard:
: 139222 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-10-06 21:29 UTC by Andrew
Modified: 2007-11-30 22:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-10-29 14:53:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Available Package Updates screen (deleted)
2004-10-06 21:31 UTC, Andrew
no flags Details

Description Andrew 2004-10-06 21:29:44 UTC
Description of problem:
up2date reports 0 kB as the size of most packages

Version-Release number of selected component (if applicable):
up2date-gnome-4.3.40-1
up2date-4.3.40-1
rhnlib-1.8-6.p23.fc3
rhn-applet-2.1.11-1


How reproducible:
Every time.

Steps to Reproduce:
1. Right click on Red Hat Alert Network Icon and select Launch up2date
2. Select defaults until you reach Available Package Updates screen
3.
  
Actual results:
See screenshot

Expected results:
Actual package sizes

Additional info:
When up2date does the "testing package set", it is possible to get an
error that indicates that it needs additional space on the filesystem,
even though the package sizes are listed as "0 kB".  Also, the "Total
size of selected packages to download" is also incorrect on this screen.
Calculating the actual space to be used would be very
processor-intensive (probably requiring several RPM transactions as is
done before installation, and to generate the error I described
above), but should this not be estimated based on the size of the
files, if not the actual information within the RPMs?  Thoughts anyone?

Comment 1 Andrew 2004-10-06 21:31:15 UTC
Created attachment 104871 [details]
Available Package Updates screen

Comment 2 Rahul Sundaram 2005-06-27 16:25:04 UTC
*** Bug 139222 has been marked as a duplicate of this bug. ***

Comment 3 John Thacker 2006-10-29 14:53:16 UTC

*** This bug has been marked as a duplicate of 107048 ***


Note You need to log in before you can comment on or make changes to this bug.