Bug 528237 - Multilib conflict in libotf-devel
Summary: Multilib conflict in libotf-devel
Alias: None
Product: Fedora
Classification: Fedora
Component: libotf
Version: 12
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Neal Becker
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2009-10-09 22:26 UTC by Philippe Troin
Modified: 2010-12-04 07:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-12-04 07:31:10 UTC
Type: ---

Attachments (Terms of Use)

Description Philippe Troin 2009-10-09 22:26:01 UTC
Description of problem:

yum install libotf-devel.i586 libotf-devel.x86_64


Transaction Check Error:
  file /usr/bin/libotf-config from install of libotf-devel-0.9.8-2.fc11.i586 conflicts with file from package libotf-devel-0.9.8-2.fc11.x86_64
  file /usr/share/doc/libotf-devel-0.9.8/example/Makefile from install of libotf-devel-0.9.8-2.fc11.i586 conflicts with file from package libotf-devel-0.9.8-2.fc11.x86_64

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

Comment 1 Neal Becker 2009-10-10 00:16:58 UTC
Try 0.9.9-2

Comment 2 Adam Williamson 2009-10-10 02:36:11 UTC
you shouldn't close a bug in a stable release until an official update package has been shipped...

Fedora Bugzappers volunteer triage team

Comment 3 Philippe Troin 2010-02-15 22:15:33 UTC
And it has not.

F12 contains libotf-devel-0.9.9-1.fc12 which still has problems.

Thus reopening.

Comment 4 Neal Becker 2010-02-16 00:12:32 UTC
I brought this up on fedora-devel list when it was first reported.  IIRC, the consensus was that this is not a bug - there is no requirement that multiple devel packages do not conflict.


Any counter argument?

Comment 5 Philippe Troin 2010-02-16 01:04:43 UTC
On a 64-bit system, I can build either a 32-bit or 64-bit binary or library by using -m32 or -m64.
If I cannot install both 32 and 64 bit -devel packages, I cannot any more.

If this is a (new) Fedora guideline, then that's fine with me.  Stupid in my opinion (as this was a big Fedora selling point for me), but fine.
Then remove all -devel.i686 packages from the repositories.
Or make both libotf-devel.i686 mutually exclusive.

In my opinion, if you're allowed to install it, it should install, not bug out.

Thanks for your time.

Comment 6 Bug Zapper 2010-11-04 09:32:54 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 WONTFIX if it remains open with a Fedora 
'version' of '12'.

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 prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 

Comment 7 Bug Zapper 2010-12-04 07:31:10 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.

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.