Jeff Johnson wrote:
A similar issue was reported @rpm.org, yum needing 2.5Gb for an
upgrade.
That problem was diagnosed as memory fragmentation within
rpmdbGrowIterator(),
mostly because its inconceivable to most that yum could somehow be
flawed.
There's a patch that can do a power of 2 block allocation in
rpmdbGrowIterator() @rpm.org,
not hard.
The failure is seen only with yum and python, and shows up with
yum's peculier
usage of rpmlib, yum chooses to call rpmtsRun() a second time.
Supposedly (have not verified it's the same issue) this also happens
with Smart when using rpm.org and python, as reported for 4.4.2.3 in:
https://bugs.launchpad.net/smart/+bug/244943
The --stepped option mentioned causes Smart to do multiple commits
(after splitting the ChangeSet), with each commit() doing a ts.run
--anders
______________________________________________________________________
RPM Package Manager http://rpm5.org
Developer Communication List rpm-devel@rpm5.org
