Bug 496131 - File conflict between openmpi and libotf in F11 rawhide branch
Summary: File conflict between openmpi and libotf in F11 rawhide branch
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openmpi
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jay Fenlason
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 520027 520074 527657 529735 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-16 19:30 UTC by Bruno Wolff III
Modified: 2014-08-31 23:29 UTC (History)
15 users (show)

Fixed In Version: 1.3.3-6.fc11
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-16 07:38:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Bruno Wolff III 2009-04-16 19:30:33 UTC
Description of problem:

Transaction Check Error:
  file /usr/bin/otfdump from install of openmpi-1.3.1-1.fc11.x86_64 conflicts with file from package libotf-0.9.8-2.fc11.x86_64


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Bug Zapper 2009-06-09 13:57:13 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Doug Ledford 2009-07-21 15:14:42 UTC
This is fixed in openmpi-1.3.3-1

Comment 3 Fedora Update System 2009-07-21 15:51:52 UTC
openmpi-1.3.3-1.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/openmpi-1.3.3-1.fc11

Comment 4 Bruno Wolff III 2009-07-21 16:09:47 UTC
I did a quick test of updating from a downloaded copy of the rpm and had a depsolve problem. Is there a missing obsoletes?

 Package       Arch      Version          Repository                       Size
================================================================================
Updating:
 openmpi       x86_64    1.3.3-1.fc11     /openmpi-1.3.3-1.fc11.x86_64    4.3 M
Installing for dependencies:
 libibverbs    x86_64    1.1.2-2.fc11     fedora                           45 k

Transaction Summary
================================================================================
Install      1 Package(s)         
Update       1 Package(s)         
Remove       0 Package(s)         

Total size: 4.4 M
Total download size: 45 k
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
ERROR with rpm_check_debug vs depsolve:
openmpi-libs is needed by (installed) R-RScaLAPACK-0.5.1-19.fc11.x86_64
Complete!
(1, [u'Please report this error in http://yum.baseurl.org/report'])

Comment 5 Bruno Wolff III 2009-07-21 16:14:49 UTC
Adding openmpi-libs to the yum updates command seems to have worked around this. So most likely it's a yum issue, not an openmpi issue.

However now I am seeing the following:

Running Transaction
  Updating       : openmpi-libs-1.3.1-1.fc11.x86_64                         1/5 
/sbin/ldconfig: /usr/lib64/libmodbc.so.0 is not a symbolic link

  Installing     : libibverbs-1.1.2-2.fc11.x86_64                           2/5 
/sbin/ldconfig: /usr/lib64/libmodbc.so.0 is not a symbolic link

  Updating       : openmpi-1.3.3-1.fc11.x86_64                              3/5 
Error in PREUN scriptlet in rpm package o
/usr/lib64/openmpi/1.2.4-gcc/openmpi.ld.conf has not been configured as an alternative for mpilibs64
Error in PREUN scriptlet in rpm package o
openmpi-libs-1.2.4-3.fc11.x86_64 was supposed to be removed but is not!
openmpi-1.2.4-3.fc11.x86_64 was supposed to be removed but is not!

Dependency Installed:
  libibverbs.x86_64 0:1.1.2-2.fc11                                              

Updated:
  openmpi.x86_64 0:1.3.3-1.fc11        openmpi-libs.x86_64 0:1.3.1-1.fc11

Comment 6 Bruno Wolff III 2009-07-21 16:24:07 UTC
I ended up using rpm and --noscripts to remove the old versions of openmpi and openmpi-libs. I still have another machine to update, and can test another update. I probably do the update sometime tomorrow using --noscripts if there isn't a new version to test by then.

Comment 7 Bruno Wolff III 2009-07-23 09:50:24 UTC
I tried openmpi-1.3.3-2.fc11.i586 on my other machine and had to use --noscripts in order to remove openmpi-1.2.4-3.fc11.i586.

Comment 8 Fedora Update System 2009-07-23 19:05:59 UTC
openmpi-1.3.3-2.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update openmpi'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-7951

Comment 9 Doug Ledford 2009-07-25 14:18:37 UTC
There are a couple things going on here.  First, yes, I should have done an Obsoletes: openmpi-libs.  Second, due to packaging changes, all openmpi linked applications will need rebuilt (well, more than just packaging changes, openmpi-1.3.2 and later are binary incompatible with previous openmpi versions, so they would need at least a recompile anyway).  We are currently discussing MPI specific packaging guidelines on the fedora-packaging list.  I expect there will be additional changes to the packaging before I push this update to stable and there will be a period of transition getting dependent packages redesigned and rebuilt to accommodate multiple MPI implementations.

Comment 10 Michael Schwendt 2009-07-25 15:10:45 UTC
With regard to the last sentence: I see it regularly that ABI/API-incompatible updates are marked stable before dependent packages have been rebuilt. This is not how it ought to be done. The proper way would be to keep the packages in updates-testing and request Fedora Release Engineering to create koji buildroot override tags for them, so all dependent packages can be rebuilt and finally be pushed together within a single bodhi ticket.

Comment 11 Doug Ledford 2009-07-27 13:42:54 UTC
I don't think you can push them together in a single bodhi ticket due to bodhi limitations.  Namely, I don't think bodhi allows someone other than the package owner to push a rebuilt package to stable, so I couldn't push someone else's dependent package.  I could be wrong (and am happy to be corrected), but that's my understanding of the difficulty in getting what you are requesting done.

Comment 12 Michael Schwendt 2009-07-27 13:53:19 UTC
Well, it might be that for packages you don't "own", it needs 'provenpackagers' membership (or cvs devel tree commit acl for the packages), but: Collecting all rebuilds in bodhi updates-testing, even if done by multiple packagers, and trying to coordinate when to push the multiple tickets at once, is still better than breaking something in "stable".

Comment 13 Doug Ledford 2009-07-27 13:57:47 UTC
Agreed, and this is why openmpi is only in testing at the moment even though given the number of various bugs this update addresses I'm sure various people would like to see it in stable sooner rather than later ;-)

Comment 14 Gwyn Ciesla 2009-08-27 13:39:17 UTC
Still conflicting, just hit F-11 stable.

Comment 15 Alex Lancaster 2009-08-28 04:30:50 UTC
*** Bug 520027 has been marked as a duplicate of this bug. ***

Comment 16 Philip Blakely 2009-08-30 15:59:14 UTC
(In reply to comment #14)
> Still conflicting, just hit F-11 stable.  

Upgrading openmpi manually to openmpi-1.3.3-2.fc11.i586 via

su -c 'yum --enablerepo=updates-testing update openmpi'

as suggested in Comment 8 above, and then re-running Software Update successfully avoided the conflict for me.

(I was upgrading from openmpi-1.3.3-1.fc11.i586.)

Comment 17 Jay Fenlason 2009-10-08 18:21:57 UTC
*** Bug 520074 has been marked as a duplicate of this bug. ***

Comment 18 Gwyn Ciesla 2009-10-20 12:07:14 UTC
Do we have an ETA on this?  Is there active work being done?

Comment 19 Doug Ledford 2009-10-20 18:24:46 UTC
*** Bug 529735 has been marked as a duplicate of this bug. ***

Comment 20 Doug Ledford 2009-10-20 18:24:58 UTC
*** Bug 527657 has been marked as a duplicate of this bug. ***

Comment 21 Fedora Update System 2009-10-20 20:55:24 UTC
openmpi-1.3.3-6.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/openmpi-1.3.3-6.fc11

Comment 22 Fedora Update System 2009-10-27 07:19:46 UTC
openmpi-1.3.3-6.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update openmpi'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-10848

Comment 23 Michael Ploujnikov 2009-10-27 12:44:02 UTC
Installing openmpi-devel-1.3.3-6.fc11.x86_64 and openmpi-devel-1.3.1-1.fc11.x86_64 worked for me.

Comment 24 Josip Šumečki 2009-10-27 14:21:33 UTC
(In reply to comment #23)
> Installing openmpi-devel-1.3.3-6.fc11.x86_64 and
> openmpi-devel-1.3.1-1.fc11.x86_64 worked for me.  

It doesn't work only if you previously installed emacs!

Comment 25 Michael Ploujnikov 2009-10-27 14:31:44 UTC
I had emacs installed from before. This is what I have now:
#rpm -q emacs openmpi
emacs-23.1-5.fc11.x86_64
openmpi-1.3.3-6.fc11.x86_64

Note that I installed openmpi from the testing repository.

Comment 26 Thomas Fitzsimmons 2009-11-09 01:14:23 UTC
On my x86_32 machine I hit this conflict and installing openmpi from updates-testing solved the problem.  I had emacs-23.1-5.fc11.i586 installed previously.

Comment 27 Gwyn Ciesla 2009-11-10 20:22:25 UTC
Sounds like a push to stable might be warranted.

Comment 28 Alex Lancaster 2009-11-12 20:57:19 UTC
By the way is dajt the new maintainer of this package rather than Doug Ledford (which I read somewhere)?  If so, Doug should release ownership of the package in PackageDB and dajt should be added:

https://admin.fedoraproject.org/pkgdb/packages/name/openmpi

so that bugs are properly assigned and Cc'ed etc.

Comment 29 Fedora Update System 2009-11-16 07:38:40 UTC
openmpi-1.3.3-6.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.


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