Bug 912324

Summary: yum check + rpmdb problems
Product: [Fedora] Fedora Reporter: Mohammed Arafa <bugzilla>
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: 18CC: 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-19 07:19:06 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 Mohammed Arafa 2013-02-18 12:12:12 UTC 
Description of problem:

Total download size: 7.7 M
Downloading Packages:
Setting up and reading Presto delta metadata
Processing delta metadata
Download delta size: 1.3 M
Presto reduced the update size by 84% (from 7.6 M to 1.3 M).
Running Transaction Check
Please report this error in https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=rawhide&component=yum
ERROR with transaction check vs depsolve:
httpd-mmn = 20051115-x86-64 is needed by (installed) mod_python-3.3.1-18.fc17.x86_64
** Found 2 pre-existing rpmdb problem(s), 'yum check' output follows:
bluegriffon-1.0-4.fc15.remi.x86_64 has missing requires of libhunspell-1.2.so.0()(64bit)
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-18.03-07.zNnvX9.yumtx

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Mohammed Arafa 2013-02-18 12:18:20 UTC 
i removed the 2 packages btw
Comment 2 Jan Zeleny 2013-02-19 07:19:06 UTC 

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