Bug 1304871 - libgccjit-devel-5.3.1-2.fc22.i686 conflicts with libgccjit-devel-5.3.1-2.fc22.x86_64
libgccjit-devel-5.3.1-2.fc22.i686 conflicts with libgccjit-devel-5.3.1-2.fc22...
Status: CLOSED EOL
Product: Fedora
Classification: Fedora
Component: gcc (Show other bugs)
22
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Jakub Jelinek
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-04 15:47 EST by Roy A. Gilmore
Modified: 2016-07-19 14:42 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-19 14:42:02 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Roy A. Gilmore 2016-02-04 15:47:33 EST
Description of problem:
libgccjit-devel-5.3.1-2.fc22.i686 conflicts with libgccjit-devel-5.3.1-2.fc22.x86_64

Version-Release number of selected component (if applicable):
libgccjit-devel-5.3.1-2.fc22.i686 and libgccjit-devel-5.3.1-2.fc22.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Install libgccjit-devel-5.3.1-2.fc22.x86_64
2. Attempt to install libgccjit-devel-5.3.1-2.fc22.i686

Actual results:
Error: Transaction check error:
  file /usr/share/doc/libgccjit-devel/html/searchindex.js from install of libgccjit-devel-5.3.1-2.fc22.i686 conflicts with file from package libgccjit-devel-5.3.1-2.fc22.x86_64

Expected results:
Success

Additional info:
Why aren't the docs in a noarch package?
Comment 1 Fedora End Of Life 2016-07-19 14:42:02 EDT
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.