[Bug 1051286] New: BuildRequires: openmpi2-devel leads to choice error
http://bugzilla.opensuse.org/show_bug.cgi?id=1051286 Bug ID: 1051286 Summary: BuildRequires: openmpi2-devel leads to choice error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: nmoreychaisemartin@suse.com Reporter: adrian@suse.com QA Contact: qa-bugs@suse.de CC: dimstar@opensuse.org Found By: --- Blocker: --- I get this dependency error when adding openmpi2-devel aus BuildRequires: unresolvable: have choice for openmpi-runtime-config needed by openmpi2: openmpi-config openmpi2-config, have choice for openmpi-runtime-config needed by openmpi: openmpi-config openmpi2-config We could solve this by prefering on of it in each prjconf (or each packager can workaround it in his spec file), but Dominque and me think it is better solved in the openmpi2 package. Is it really true that openmpi2 is find with the openmpi version 1 config? Doesn't it make sense the openmpi2 requires the openmp2-config ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1051286
http://bugzilla.opensuse.org/show_bug.cgi?id=1051286#c1
--- Comment #1 from Nicolas Morey-Chaisemartin
I get this dependency error when adding openmpi2-devel aus BuildRequires:
unresolvable: have choice for openmpi-runtime-config needed by openmpi2: openmpi-config openmpi2-config, have choice for openmpi-runtime-config needed by openmpi: openmpi-config openmpi2-config
We could solve this by prefering on of it in each prjconf (or each packager can workaround it in his spec file), but Dominque and me think it is better solved in the openmpi2 package.
Is it really true that openmpi2 is find with the openmpi version 1 config?
Yes
Doesn't it make sense the openmpi2 requires the openmp2-config ?
Yes and no :) To explain, openmpi 1, 2 (and soon 3) provide exactly the same config file. The intent with this trick is to allow installing multiple versions of MPI at once. Any *-config will suffice as they contain the same stuff. The nicer trick would be to have OBS behave the way zypper do. Because of the Recommends in the spec, zypper does not have this kind of issue... But I'm open to better solutions. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1051286
http://bugzilla.opensuse.org/show_bug.cgi?id=1051286#c2
--- Comment #2 from Adrian Schröter
http://bugzilla.opensuse.org/show_bug.cgi?id=1051286
http://bugzilla.opensuse.org/show_bug.cgi?id=1051286#c3
--- Comment #3 from Nicolas Morey-Chaisemartin
However, what is the point of having multiple -config packages then in openSUSE:Factory if any of them should just work? How is the user supposed to decide?
He does not need to decide and that's the point. It also means that the spec/packjage for OpenMPI are the same in all coming SUSE release and do not depend on what versions are available. If we want to have only one, from which openmpi version should we produce the -config RPM ? Depending on the OS release, different openmpi packages are available (openmpi1 will soon be replaced by openmpi3 for example) The current way makes maintenance easier as we can keepo the package in sync whatever versions are available. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com