Bug 1110655

Summary:	libunwind-devel.i686 and libunwind-devel.x86_64 conflict
Product:	[Fedora] Fedora	Reporter:	Konstantin Belousov <kostikbel>
Component:	libunwind	Assignee:	Kyle McMartin <kmcmartin>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	20	CC:	kmcmartin, kostikbel, peterm, suckfish, urkle
Target Milestone:	---	Flags:	urkle: needinfo? (kmcmartin)
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-29 21:11:28 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:
Embargoed:

Description Konstantin Belousov 2014-06-18 07:39:30 UTC

I have libunwind-devel-1.1-3.fc20.x86_64 installed.  Attempt to install 32bit devel rpm for libunwind results in conflict:

# yum install  libunwind-devel.i686
...

Transaction check error:
  file /usr/include/libunwind.h from install of libunwind-devel-1.1-3.fc20.i686 conflicts with file from package libunwind-devel-1.1-3.fc20.x86_64

Comment 1 Ralph Loader 2014-08-30 01:54:24 UTC

Inspecting the source code, this is an upstream problem.

If Fedora wants to fix, then they could just remove the #ifdef logic to support UNW_REMOTE_ONLY, leaving only the generic non-UNW_REMOTE_ONLY case (i.e., keep just the chain of architect #ifdef's).

Comment 2 Ralph Loader 2014-08-30 02:08:29 UTC

> Inspecting the source code, this is an upstream problem.

I reported this upstream:

https://savannah.nongnu.org/bugs/?43108

Comment 3 Fedora End Of Life 2015-05-29 12:09:02 UTC

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-06-29 21:11:28 UTC

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.

Comment 5 Edward Rudd 2016-11-11 01:22:41 UTC

This is still an issue in Fedora 24.