After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 592074 - Need to 'yum clean all' for gnome repo
Need to 'yum clean all' for gnome repo
Status: RESOLVED FIXED
Product: sysadmin
Classification: Infrastructure
Component: Packages
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Sysadmins
GNOME Sysadmins
Depends on:
Blocks:
 
 
Reported: 2009-08-17 13:04 UTC by Owen Taylor
Modified: 2011-10-03 16:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Owen Taylor 2009-08-17 13:04:45 UTC
I've observed in the past that when I update the GNOME repository (by putting packages into /home/admin/pkgs and then running 'cobbler reposync' on container), that I'm not able to install the new packages without running 'yum clean all' on the affected machine. ['all' is more aggressive then is needed, but saves thinking]

Couple things that could be going on:

 - Maybe the yum is simply not even checking for updated meta-data if it's checked at some point in the fairly recent past. There might be some per-repository parameter that could be configured to be short for the gnome repository (since it's small and local.)

 - Maybe there is a cobbler bug that is not updating timestamps properly (we updated our cobbler version on container recently, I haven't tested carefully for this problem after that upgrade. It's conceivable that this bug is not still happening.)

Needs testing to see if it's still happening and better characterize the problem, and then if necessary fixing.
Comment 1 Owen Taylor 2011-10-03 16:15:39 UTC
Author: Owen W. Taylor <otaylor@fishsoup.net>
Date:   Mon Oct 3 12:10:09 2011 -0400

    packages: change metadata_expire for local repositories to 5 minutes
    
    Once we install a new package into our repositories, we want it to
    be available almost immediately, so change the timeout for checking
    for new metadata to 5 minutes.
    
    ('yum clean expire-cache' to force checking immediately.)