[SOLVED] .PKGINFO files specify wrong installation sizes

MarianCJC · 2012-02-22 12:01:30

Today I was about to do a full system upgrade (pacman -Syu)
The only things needing upgrading are libmysqlclient, mysql, mysql-clients
So pacman tells me:

Total download size: 12.17 MiB
Total installed size: 85.91 MiB
Net upgrade size: -28.94 MiB

Usually this happens when packages are removed during installation/upgrade of other packages.
Since there's really no difference in size for the source of the packages, or the packages themselves...
..what other things does pacman deletes?

edit
----
One issue I found while trying to figure this out:
Extracting the new package (for mysql) mysql-5.5.21-1-x86_64.pkg.tar.xz with tar -Jxvf gives this error/notice:
tar: Ignoring unknown extended header keyword `SCHILY.flags'
This does not happen for 5.5.20
Also:
Looks like pacman doesn't actually deletes the 28 megs, the problem is in the .PKGINFO file from 2 of the 3 packages, for example:
mysql 5.5.20: size=77074432
mysql 5.5.21: size=62255104
even if the actual sizes of the extracted information are pretty much the same

Question now is, is this a bug of 5.5.21 package?

Last edited by MarianCJC (2012-02-22 13:46:07)

ilpianista · 2012-02-22 12:51:12

Confirmed.

Name Old Version New Version Net Change Download Size
libmysqlclient 5.5.20-1 5.5.21-1 -14.85 MiB
mysql 5.5.20-1 5.5.21-1 -14.13 MiB
mysql-clients 5.5.20-1 5.5.21-1 0.04 MiB
Total Installed Size: 85.91 MiB
Net Upgrade Size: -28.94 MiB

There're no missing files, but the 5.5.21 tarballs shows that warning (error?) when extracting.

EDIT:
You get that warning if you try to extract every package recently built.

EDIT2:
Also, sizes are similar, I guess this is a bug in pacman.

$ ls -al /var/cache/pacman/pkg/*5.5.20*
-rw-r--r-- 1 root root 3080092 Jan 12 09:03 /var/cache/pacman/pkg/libmysqlclient-5.5.20-1-x86_64.pkg.tar.xz
-rw-r--r-- 1 root root 287 Jan 12 09:03 /var/cache/pacman/pkg/libmysqlclient-5.5.20-1-x86_64.pkg.tar.xz.sig
-rw-r--r-- 1 root root 8604484 Jan 12 09:03 /var/cache/pacman/pkg/mysql-5.5.20-1-x86_64.pkg.tar.xz
-rw-r--r-- 1 root root 287 Jan 12 09:03 /var/cache/pacman/pkg/mysql-5.5.20-1-x86_64.pkg.tar.xz.sig
-rw-r--r-- 1 root root 840192 Jan 12 09:03 /var/cache/pacman/pkg/mysql-clients-5.5.20-1-x86_64.pkg.tar.xz
-rw-r--r-- 1 root root 287 Jan 12 09:03 /var/cache/pacman/pkg/mysql-clients-5.5.20-1-x86_64.pkg.tar.xz.sig
$ ls -al /var/cache/pacman/pkg/*5.5.21*
-rw-r--r-- 1 root root 3084936 Feb 21 08:30 /var/cache/pacman/pkg/libmysqlclient-5.5.21-1-x86_64.pkg.tar.xz
-rw-r--r-- 1 root root 287 Feb 21 08:30 /var/cache/pacman/pkg/libmysqlclient-5.5.21-1-x86_64.pkg.tar.xz.sig
-rw-r--r-- 1 root root 8832520 Feb 21 08:30 /var/cache/pacman/pkg/mysql-5.5.21-1-x86_64.pkg.tar.xz
-rw-r--r-- 1 root root 287 Feb 21 08:30 /var/cache/pacman/pkg/mysql-5.5.21-1-x86_64.pkg.tar.xz.sig
-rw-r--r-- 1 root root 840052 Feb 21 08:30 /var/cache/pacman/pkg/mysql-clients-5.5.21-1-x86_64.pkg.tar.xz
-rw-r--r-- 1 root root 287 Feb 21 08:30 /var/cache/pacman/pkg/mysql-clients-5.5.21-1-x86_64.pkg.tar.xz.sig

MarianCJC · 2012-02-22 13:07:58

I think the .PKGINFO files in the packages are to blame, they report wrong size

ilpianista · 2012-02-22 13:11:49

Then is a bug in makepkg.

falconindy · 2012-02-22 13:26:35

MarianCJC wrote:

Today I was about to do a full system upgrade (pacman -Syu)
The only things needing upgrading are libmysqlclient, mysql, mysql-clients
So pacman tells me:
Total download size: 12.17 MiB
Total installed size: 85.91 MiB
Net upgrade size: -28.94 MiB

Usually this happens when packages are removed during installation/upgrade of other packages.
Since there's really no difference in size for the source of the packages, or the packages themselves...
..what other things does pacman deletes?
edit
----
One issue I found while trying to figure this out:
Extracting the new package (for mysql) mysql-5.5.21-1-x86_64.pkg.tar.xz with tar -Jxvf gives this error/notice:
tar: Ignoring unknown extended header keyword `SCHILY.flags'
This does not happen for 5.5.20
Also:
Looks like pacman doesn't actually deletes the 28 megs, the problem is in the .PKGINFO file from 2 of the 3 packages, for example:
mysql 5.5.20: size=77074432
mysql 5.5.21: size=62255104
even if the actual sizes of the extracted information are pretty much the same
Question now is, is this a bug of 5.5.21 package?

Looks like this was already fixed in master, but hasn't been released.

FYI, I recommend using bsdtar(1) over GNU tar(1). pacman exclusively uses libarchive to create/handle archives, and it understands this flag.

MarianCJC · 2012-02-22 13:43:48

Thanks for the info, I was just about report a bug about this,
I'm going to mark this topic as solved, since this is a known(solved) issue

Arch Linux

#1 2012-02-22 12:01:30

[SOLVED] .PKGINFO files specify wrong installation sizes

#2 2012-02-22 12:51:12

Re: [SOLVED] .PKGINFO files specify wrong installation sizes

#3 2012-02-22 13:07:58

Re: [SOLVED] .PKGINFO files specify wrong installation sizes

#4 2012-02-22 13:11:49

Re: [SOLVED] .PKGINFO files specify wrong installation sizes

#5 2012-02-22 13:26:35

Re: [SOLVED] .PKGINFO files specify wrong installation sizes

#6 2012-02-22 13:43:48

Re: [SOLVED] .PKGINFO files specify wrong installation sizes

Board footer