Bug 727138

Summary: libdb i686 is missing in x86_64 repository
Product: [Fedora] Fedora Reporter: The Source <thesource>
Component: distributionAssignee: Bill Nottingham <notting>
Status: CLOSED ERRATA QA Contact: Bill Nottingham <notting>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: dennis, jnovy, kurik, rdieter, rvokal
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: 2012-01-04 22:16:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 729250    
Bug Blocks:    

Description The Source 2011-08-01 12:14:51 UTC 
Description of problem:
32bit libdb package is missing which prevents some packages (like cyrus-sasl) from updating/installing

Version-Release number of selected component (if applicable):
libdb-5.1.25-2.fc15

How reproducible:


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


Expected results:


Additional info:
Comment 1 Jindrich Novy 2011-08-02 08:53:29 UTC 
Is it possible to include the i686 package for x86_64?
Comment 2 Bill Nottingham 2011-08-02 14:17:40 UTC 
That will happen as soon as something that depends on it is included as an update. (It's an issue with how the library is named).

We can push a fix in mash to automatically handle this, but it will take a while to propagate.
Comment 3 Bill Nottingham 2011-08-02 14:26:47 UTC 
*** Bug 727515 has been marked as a duplicate of this bug. ***
Comment 4 Bill Nottingham 2011-08-02 14:38:02 UTC 
Actually, setting parent_repos properly should handle this.
Comment 5 kurik 2011-08-02 18:37:14 UTC 
Can you, please, give some example how to set correctly the parent_repos ?
Comment 6 Bill Nottingham 2011-08-02 18:44:38 UTC 
It's a mash configuration option when creating the update repositories; it's not a user option.
Comment 7 Bill Nottingham 2012-01-04 22:16:21 UTC 
This is now fixed.