Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 64949

Summary: glibc-common package ain't so big
Product: [Retired] Red Hat Linux Reporter: Need Real Name <d-lewart>
Component: rpmAssignee: Jeff Johnson <jbj>
Status: CLOSED WONTFIX QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: low    
Version: 7.3CC: katzj
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
URL: http://groups.google.com/groups?selm=20020117092849.J12158@eastham.redhat.com
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-07-02 05:46:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Need Real Name 2002-05-14 23:53:27 UTC
Description of Problem:
* The glibc-common RPM cleverly uses hard links and PartialHardlinkSets
* This makes the package installer wildly overstate the package size
* This will needlessly scare people with small disk drives
* It causes the "Time Remaining" values to too small


Version-Release number of selected component (if applicable):


How Reproducible:
* Install Red Hat Linux 7.3


Steps to Reproduce:
1. Install Red Hat Linux 7.3 ...
2. Select only English as the language
3. Watch the pretty "Installing Packages" display


Actual Results:
* It says glibc-common has a size of 182,860 KBytes


Expected Results:
* glibc-common should have a size of ~10,588 KBytes


Additional Information:
* How is package size calculated anyway?
* Even if it is too difficult to calculate the package size based on
  the selected languages, it should be possible to estimate it based
  on the number of languages.

Comment 1 Jeremy Katz 2002-07-02 05:46:18 UTC
We're just using the size tag in the packages

Comment 2 Jeff Johnson 2002-07-02 13:26:15 UTC
The package size is the sum of all
the file sizes, ignoring hardlinks.

The actual installed package size depends on
install parameters such as desired locales
and cannot be computed at build time.

Sure estimates are possible, the current estimate
of the installed package size is the sum of all
the file sizes, ignoring hardlinks :-)