Bug 1310423 - Can't upgrade to graphite2-1.3.5-1.fc22.x86_64
Summary: Can't upgrade to graphite2-1.3.5-1.fc22.x86_64
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: graphite2
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nicholas van Oudtshoorn
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-21 12:54 UTC by Peter H. Jones
Modified: 2016-07-19 18:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 18:44:21 UTC
Type: Bug


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.