Rahul Sundaram wrote:
On Sun, 2006-06-25 at 11:55 -0400, Richard Hally wrote:
> Florian La Roche wrote:
>> On Sun, Jun 25, 2006 at 08:15:02AM -0700, darrell pfeifer wrote:
>>> I'm updating a rawhide system that hasn't seen an update
>>> in about a month. The yum update managed to download 750 meg
>>> of rpms but didn't have enough disk space to install them.
>>>
>>> I ran update on gnome, then kde. Yum used the cached
>>> files. I decided to update yum itself. On the next update
>>> yum rebuilt the sqlite cache. Subsequent yum updates are
>>> now downloading the rpm's again, ignoring about 500 meg
>>> of files sitting in /var/cache/yum.
>>>
>>> Is this a bug or expected behaviour?
>> New expected behaviour. To get the old default behaviour,
>> you can set "metadata_expire=0" in the main or per-repo
>> section.
>>
>> regards,
>>
>> Florian La Roche
>>
> Huh? Re-download RPMs it already has in it's cache, why would it be
> designed to do that?
Are you sure it retains the packages? If it does have it in cache,
redownloading would of course be a bug but the default behavior doesnt
retain it anymore.
Rahul
So, the correct answer to the OP would have included something like
"default behavior has changed, look at /etc/yum.conf and set
keepcache=1" to retain packages in cache.
Richard