Hi Erik,
Sorry for not getting back to you earlier...
On 30/06/16 10:12, Erik Smeets wrote:
Hi Kenneth,
-----Original Message-----
What would be the correct solution to this issue when using dependency
issues/conflicts like this in EasyBuild?
Your conclusion is correct, but not entirely: the conflict is reported on on
libX11 that does not have a versionsuffix
(libx11/1.6.3-intel-2016.03-GCC-5.3) with one that *does* have a
(Python) versionsuffix (libx11/1.6.3-intel-2016.03-GCC-5.3-Python-2.7.10).
So, it seems it's not the libX11 dep in Qt that is to blame.
Since EasyBuild requires strict versioning (which includes version suffixes),
you'll need to make sure you use one or the other.
Is there a way (eb option) to enforce one or the other? Or do I need to create
a new eb-file for this? I mean, when installing Paraview with the robot option
it automagically installs all dependencies but then it hits this conflict.
No, there's no.
When EasyBuild runs into a version conflict, it just stops, since it's
considered an error.
The upcoming EasyBuild release has support for "eb --check-conflicts"
which allows you to detect conflicts without having to go through the
whole build, and to more easily figure out where the conflicts come from
(see https://github.com/hpcugent/easybuild-framework/pull/1833).
regards,
Kenneth
