Bug 880665

Summary: Installing big package frees storage
Product: [openSUSE] openSUSE 13.1 Reporter: Andreas Schwab <schwab>
Component: libzyppAssignee: Michael Schröder <mls>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: adrian.schroeter, qantas94heavy
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Andreas Schwab 2014-05-30 07:24:26 UTC
When Installing a big package zypper claims that it has a negative size.

The following NEW package is going to be installed:
  kernel-desktop-debuginfo 

1 new package to install.
Overall download size: 324.2 MiB. After the operation, 1.6 GiB will be freed.
Continue? [y/n/? shows all options] (y): 
Retrieving package kernel-desktop-debuginfo-3.14.4-1.1.gbebeb6f.x86_64
                                           (1/1), 324.2 MiB (-1.62 GiB unpacked)

The real size is 2.4GiB.  yast2 sw_single has the same problem, though it displays the correct info for the installed package.
Comment 1 Michael Andres 2014-05-30 11:35:41 UTC
Looks like the repo metadata contain negative size values:

 http://download.opensuse.org/debug/update/13.1:

$ zgrep -h 'installed=\|<name' *primary.xml.gz| grep -1 kernel-desktop-debuginfo 
  <size package="2698986" installed="15492045" archive="15513512"/>
  <name>kernel-desktop-debuginfo</name>
  <size package="290641930" installed="1463983472" archive="1466344636"/>
  <name>kernel-desktop-debuginfo</name>
  <size package="290696899" installed="1464180844" archive="1466533212"/>

  <name>kernel-desktop-debuginfo</name>
  <size package="300257124" installed="-2054256939" archive="-2051911468"/>

  <name>kernel-desktop-debuginfo</name>
  <size package="300387751" installed="-2053956579" archive="-2051619840"/>
Comment 2 Michael Andres 2014-05-30 11:43:50 UTC
@mls: createrepo bug?
Comment 3 Michael Schröder 2014-06-02 11:30:38 UTC
Again? Didn't we have a workaround for this?
Comment 4 Karl Cheng 2017-11-18 10:31:10 UTC
Seems to be the same issue with OBS infrastructure, which should have been fixed long ago.

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