Bug 913224

Summary: ERROR with transaction check vs depsolve: httpd-mmn = 20051115-x86-64 is needed by (installed) mod_python-3.3.1-18.fc17.x86_64
Product: [Fedora] Fedora Reporter: Harold Miller <hamiller>
Component: yumAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: admiller, ffesti, jzeleny, packaging-team-maint, tim.lauridsen, zpavlas
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: 2013-02-20 16:52:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Harold Miller 2013-02-20 16:49:44 UTC 
Description of problem:yum update failed to run


Version-Release number of selected component (if applicable):


How reproducible: easy - run yum  update


Steps to Reproduce:
1.
2.
3.
  
Actual results:
Running Transaction Check
ERROR with transaction check vs depsolve:
httpd-mmn = 20051115-x86-64 is needed by (installed) mod_python-3.3.1-18.fc17.x86_64
Please report this error in https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=rawhide&component=yum
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
mod_python-3.3.1-18.fc17.x86_64 has missing requires of httpd-mmn = ('0', '20051115', 'x86-64')
Your transaction was saved, rerun it with:
 yum load-transaction /tmp/yum_save_tx.2013-02-20.08-33.SSCxLi.yumtx



Expected results:
Yum update completes successfully

Additional info:
uname -a
Linux laptop1.miller.priv 3.7.6-201.fc18.x86_64 #1 SMP Mon Feb 4 15:54:08 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Fedora release 18 (Spherical Cow)
Comment 1 Jan Zeleny 2013-02-20 16:52:04 UTC 

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