Comment:

libparallelproj which is part of the conda-forge package parallelproj contains C/CUDA libs consumed / linked by other projects - e.g. STIR (also on conda-forge).

Recently, the maintainer of STIR and the STIR conda-forge feedstock reported this issue occurring at the loading stage of libparallelproj caused by different versions used for building and when installing.

Because of that, I assume libparallelproj is a candidate to be added to conda-forge-pinning?
Or should the pinning be done manually in the STIR recipe?
Or do I need to define a run_export in the parallelproj recipe?

I am using semantic versioning for libparallelproj, so in principle STIR built with libparallelproj v1.7.1 should run with v1.7.3 - so I am also a bit lost on why there is a problem in the loading stage