Bug 1310423

Summary: Can't upgrade to graphite2-1.3.5-1.fc22.x86_64
Product: [Fedora] Fedora Reporter: Peter H. Jones <jones.peter.busi>
Component: graphite2Assignee: Nicholas van Oudtshoorn <vanoudt>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: vanoudt
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: 2016-07-19 18:44:21 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:

Description Peter H. Jones 2016-02-21 12:54:35 UTC 
Description of problem:
Can't upgrade to version graphite2-1.3.5-1.fc22.x86_64.

Version-Release number of selected component (if applicable):
graphite2-1.3.5-1.fc22.x86_64

How reproducible:
Every time.

Steps to Reproduce:
1. dnf install graphite2-1.3.5-1.fc22.x86_64.rpm

Actual results:
"...
Running transaction check
Transaction check succeeded.
Running transaction test
Error: Transaction check error:
  file /usr/share/doc/graphite2/ChangeLog from install of graphite2-1.3.5-1.fc22.x86_64 conflicts with file from package graphite2-1.2.4-3.fc22.i686

Error Summary
-------------

"


Expected results:
Successful upgrade.

Additional info:
Comment 1 Fedora End Of Life 2016-07-19 18:44:21 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.