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. Kind regards, Erik Smeets [Erik Smeets] -- The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. Unless explicitly stated otherwise in the body of this communication or the attachment thereto (if any), the information is provided on an AS-IS basis without any express or implied warranties or liabilities. To the extent you are relying on this information, you are doing so at your own risk. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. The sender nor the company/group of companies he or she represents shall be liable for the proper and complete transmission of the information contained in this communication, or for any delay in its receipt.
