Mailinglist Archive: opensuse-buildservice (178 mails)

< Previous Next >
Re: [opensuse-buildservice] how to solve "unresolvable: have choice for"
  • From: Adrian Schröter <adrian@xxxxxxx>
  • Date: Wed, 26 Sep 2012 13:25:42 +0200
  • Message-id: <2848544.kvkAtfsPS2@scherben>
Am Mittwoch, 26. September 2012, 12:29:56 schrieb Ruediger Meier:

Sometimes I have such unresolable conflicts and I've never understood
what is the right way how to fix them.

For example nowadays we have two packages libhdf5-0 and
libhdf5-0-openmpi both providing

One of my packages (unsermarkt) requires "uterus" which auto-requires
So when building unsermarkt I get
unresolvable: have choice for needed by uterus:
libhdf5-0-openmpi libhdf5-0

I can solve this by adding explicitly
BuildRequires: libhdf5-0
but this is bad because this dependency comes indirectly from uterus and
might be changed there.

I also tried playing with combinations of
BuildConflicts: libhdf5-0 libhdf5-0-openmpi
but this always results in not having libhdf5-* installed at all
BTW where can I find a documentation of the BuildConflicts tag?

Right, you want at least one of them, so you can not ignore both
You may want to use instead

#!BuildIgnore: libhdf5-0-openmpi


Also I wonder what is the real purpose of hdf5's baselibs.conf:
requires -<targettype>
requires "libhdf5-0-<targettype> = <version>"
requires "libhdf5_hl0-<targettype> = <version>"
requires -openmpi-<targettype>
requires "libhdf5-0-openmpi-<targettype> = <version>"
requires "libhdf5_hl0-openmpi-<targettype> = <version>"
requires -openmpi-<targettype>
requires "libhdf5-0-mvapich2-<targettype> = <version>"
requires "libhdf5_hl0-mvapich2-<targettype> = <version>"

Is this something which should avoid such conflicts too?

No, it is just for exporting 32bit libs via extra -32bit packages to the 64bit

Thanks for clearing up,

Adrian Schroeter
SUSE Linux Products GmbH
email: adrian@xxxxxxx

To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups