[Yum-devel] Re: yum broken in testing-updates? (FC4)

[seth vidal]

On Thu, 2005-12-01 at 21:09 +0200, Panu Matilainen wrote:
> On Thu, 2005-12-01 at 13:58 -0500, seth vidal wrote:
> > On Thu, 2005-12-01 at 19:52 +0200, Panu Matilainen wrote:
> > > On Thu, 2005-12-01 at 12:11 -0500, Jeff Spaleta wrote:
> > > > On 12/1/05, Jose' Matos <jamatos at fc.up.pt> wrote:
> > > > > This will go no matter how repositories I disable. Is this a bug or a new way
> > > > > to deal with it in 2.4.1?
> > > > 
> > > > this test version of yum has a new cache feature to cache
> > > > repodata..for a period of time.
> > > > Go into your yum cache directory and look for cachecookie  files for each repo.
> > > > 
> > > > The clean all is NOT cleaning out the cookie files.. which are
> > > > controlling the timeout based caching feature. This is a bug... you
> > > > need to file it.
> > > 
> > > The attached patch adds 'clean cookies' operation + cleans them on 'yum
> > > clean all' operation as well. Didn't commit to yum cvs yet since I
> > > started wondering do we really want to call them "cookies" in the user
> > > interface?
> > 
> > 1. removing fedora-test-list from the cc b/c of useless histrionics
> > there.
> > 
> > 2. I think we should just add the cache clean out to the yum clean
> > metadata subroutine 
> 
> I could imagine wanting just to force the cookies to be reset, not all
> of metadata (which can on slower machines take quite a while to
> regenerate), that's why I added it as a separate operation in the patch,
> but no grand feelings about it either way.
> 
> > and add call into yum makecache to set
> > metadata_expire = 0 for the global config and all repo configs, then
> > run.
> 
> Nod.
> 

check it in and if you could patch it for -HEAD, too that'd be nice.

thanks
-sv