Bug 723353

Summary: Updates do not install
Product: [Fedora] Fedora Reporter: Rusty <wmoncsko>
Component: asteriskAssignee: Jeffrey C. Ollie <jeff>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 14CC: extras-orphan, itamar, jeff, notting
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: 2011-07-21 01:00:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Screenshot of the update and the error
none
Screenshot of the update and the error isolated to show the error more clear. none

Description Rusty 2011-07-19 21:28:17 UTC
Created attachment 513883 [details]
Screenshot of the update and the error

Description of problem: The latest update will not install


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


How reproducible:
There are 13 updates to install.

Steps to Reproduce:
1.
2.
3.
  
Actual results: A conflict between some libraries prohibit the installation of the update,


Expected results:


Additional info: See the attached screen shot that shows the updates and the package problems.

Comment 1 Rusty 2011-07-20 01:17:32 UTC
Created attachment 513902 [details]
Screenshot of the update and the error isolated to show the error more clear.

Installed the upgrades one at a time and found that the package of:
  - Open Source PBX and
  - SELinux policy configuration
have a conflict of files as displayed in the screenshot just attached.

Comment 2 Rusty 2011-07-20 20:59:32 UTC
Working on resolving this and was able to install the SELinux configuration fix by singly installing one of the lower level options and the dependencies asked for the parent and then all installed.

Comment 3 Jeffrey C. Ollie 2011-07-20 23:46:18 UTC
Basically, the solution is not to have asterisk and callweaver installed at the same time.  Callweaver started out as a fork of asterisk so many of the binaries have the same name.  Callweaver is pretty much a dead project so I'll probably just add an explicit conflicts the next time I send out a new release.

Comment 4 Rusty 2011-07-21 01:00:36 UTC
Thank you - callweaver is removed. Apparently, this specific package came in as part of a dependency.

Thanks Again.  CLOSED - NOT A BUG.!