Bug 727582

Summary: createrepo calling for yum version not available
Product: [Fedora] Fedora Reporter: Nathan Owe <ndowens04>
Component: createrepoAssignee: Luke Macken <lmacken>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: gwync, james.antill, lmacken, pfrields
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-02 15:10:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nathan Owe 2011-08-02 14:20:29 UTC
Description of problem:
createrepo is requiring yum >= 3.2.29-8 though only yum = 3.2.29-7 is available
Which is causing yum update to give error:

--> Finished Dependency Resolution
Error: Package: createrepo-0.9.9-4.fc15.noarch (updates)
           Requires: yum >= 3.2.29-8
           Installed: yum-3.2.29-7.fc15.noarch (@updates)
               yum = 3.2.29-7.fc15
           Available: yum-3.2.29-4.fc15.noarch (fedora)
               yum = 3.2.29-4.fc15
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Version-Release number of selected component (if applicable):
createrepo-0.9.9-4.fc15.noarch (updates)

How reproducible:
everytime

Steps to Reproduce:
1.yum update

  
Actual results:
Error: Package: createrepo-0.9.9-4.fc15.noarch (updates)
           Requires: yum >= 3.2.29-8
           Installed: yum-3.2.29-7.fc15.noarch (@updates)
               yum = 3.2.29-7.fc15
           Available: yum-3.2.29-4.fc15.noarch (fedora)
               yum = 3.2.29-4.fc15
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Expected results:
Packages to be updated

Comment 1 Gwyn Ciesla 2011-08-02 15:10:48 UTC

*** This bug has been marked as a duplicate of bug 727551 ***