Bug 860082

Summary: yum says "data still to download: 856 k" but it ends downloading 4.6 MB
Product: [Fedora] Fedora Reporter: Reartes Guillermo <rtguille>
Component: yumAssignee: Fedora Packaging Toolset Team <packaging-team>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 17CC: ffesti, maxamillion, packaging-team, tim.lauridsen, zpavlas
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-25 14:31:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
yum update output none

Description Reartes Guillermo 2012-09-24 22:12:30 UTC
Created attachment 616751 [details]
yum update output

Description of problem:

When performing a yum update:

Finishing rebuild of rpms, from deltarpms <locally rebuilding
deltarpms>  | 178 MB 00:01     
Presto reduced the update size by 82% (from 178 M to 32 M).
Package(s) data still to download: 856 k

ok, but yum downloaded 4.6Mb instead of 856Kb. I never noticed
such a discrepancy before. 

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

How reproducible:
once (never noticed before)

Steps to Reproduce:
1. yum update
  
Additional info:
yum works ok, but it looks like the reported data 'still to download' is wrong.
no issues aside from that.

Comment 1 Zdeněk Pavlas 2012-09-25 14:31:20 UTC
> Presto reduced the update size by 82% (from 178 M to 32 M).
         ^^^^^^^^^^^^^^^^^^^^^^^
> Package(s) data still to download: 856 k

IIRC the "still to download" figure does not include "to be installed" packages.
There's been a similar (closed as notabug) RHEL BZ, but I can't find it ATM.

Comment 2 Zdeněk Pavlas 2012-09-25 14:36:35 UTC

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