[Rpm-metadata] createrepo doesn't handle RPMs larger than 2.0GB correctly

Zdenek Pavlas zpavlas at redhat.com
Mon Aug 12 14:36:34 UTC 2013

> Hi everyone, I'm using createrepo 0.9.8 and I have a package in my repository
> that is 8.7GB in size. The package itself installs correctly if I just
> install the RPM manually, but I cannot integrate it successfully with my
> repo. After I run createrepo, and run a yum install from the client machine,
> yum sees the package as listed as 2.0GB - which causes yum to fail during
> the download.

I've tested with createrepo-0.9.9-18.fc19 and yum-3.4.3-105.fc19
that both the primary.xml and the sqlite database contains valid data:

$ dd if=/dev/zero bs=1k count=5M >>testrepo/alacarte-0.13.4-4.fc17.noarch.rpm
$ createrepo testrepo
$ bzip2 -dc testrepo/repodata/*-primary.sqlite.bz2 >primary.sqlite
$ sqlite3 primary.sqlite 'select max(size_package) from packages'
$ ls -l testrepo/alacarte-0.13.4-4.fc17.noarch.rpm 
-rw-rw-r--. 1 zpavlas zpavlas 5368836793 Aug 12 16:19 testrepo/alacarte-0.13.4-4.fc17.noarch.rpm

Seems the problem is on the client.. Could you uncompress and check
the generated primary.sqlite to confirm this?

More information about the Rpm-metadata mailing list