Bug 702073

Summary: RFE: yum cache to understand when repo. definitions change, and force cache reload
Product: [Fedora] Fedora Reporter: Jim Kinney <jim.kinney>
Component: yumAssignee: Seth Vidal <skvidal>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 14CC: ffesti, james.antill, maxamillion, pmatilai, tla
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 15:50:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jim Kinney 2011-05-04 17:02:32 UTC
Description of problem: yum fails to recognize the distro type changed between the cache and the online repo after a repo correction


Version-Release number of selected component (if applicable):
yum-3.2.28-5.fc14

How reproducible:
always

Steps to Reproduce:
1. installed el6 spacewalk repo from yum on f14 system by mistake
2. yum install spacewalk-postgresql
3. yum install fails due to wrong (newer) python environment installed
4. yum remove spacewalk-repo; yum install correct spacewalk-repo
5. yum install spacewalk-postgresql still fails as new repo has same name and package names have same version BUT differ at the distro level.
  
Actual results:
Error: Package: spacewalk-backend-sql-1.4.39-1.el6.noarch (spacewalk)
           Requires: python(abi) = 2.6
           Installed: python-2.7-8.fc14.1.x86_64 (@anaconda-InstallationRepo-201010211827.x86_64)
               python(abi) = 2.7
           Available: python3-3.1.2-14.fc14.i686 (fedora)
               python(abi) = 3.1
...

Expected results:
expected yum to recognize the packages in cache were NOT the same and re-download as required.
Expect yum to give an error about incorrect release or version mismatch.

Additional info:
yum clean all solves problem.

Comment 1 James Antill 2011-05-04 17:55:09 UTC
 I'm guessing that when you got the new URL for the repo. the repomd.xml was older than the existing one ... so yum ignored it due to the "I must have hit an older mirror" code.

 Do the spacewalk repos. uses mirrors, or just a single baseurl?

 Do the spacewalk repos. use distro. tags that are different between Fed-14/EL6? (repolist -v).

 In fact can just just paste the repo. definition?

Comment 2 Jim Kinney 2011-05-04 18:48:57 UTC
They use a single baseurl:

[spacewalk]
name=Spacewalk
baseurl=http://spacewalk.redhat.com/yum/1.4/RHEL/6/$basearch/
gpgkey=http://spacewalk.redhat.com/yum/RPM-GPG-KEY-spacewalk-2010
enabled=1
gpgcheck=1

and

[spacewalk]
name=Spacewalk
baseurl=http://spacewalk.redhat.com/yum/1.4/Fedora/14/$basearch/
gpgkey=http://spacewalk.redhat.com/yum/RPM-GPG-KEY-spacewalk-2010
enabled=1
gpgcheck=1

Sample package names:
spacewalk-postgresql-1.3.3-1.fc14.noarch.rpm
spacewalk-postgresql-1.3.3-1.el6.noarch.rpm

Comment 3 Fedora End Of Life 2012-08-16 15:50:19 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping