-
-
Notifications
You must be signed in to change notification settings - Fork 494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adding libparallelproj to conda-forge-pinning-feedstock #5447
Comments
You should be:
|
@xhochy : thanks a lot for the feedback! I am struggling to understand how the What we need is that respects semantic versioning meaning that an application build with |
Yes, this means you are missing a |
Could you also explain what: |
For a migration, you can see the following PR as an example: https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/5824/files It will take care that all repositories that depend on a package are rebuilt in topological order with the package pinned to the same versions. |
Many thanks again! So if I understand correctly, I will submit a PR containing
and the time stamp is the time stamp of the submission? |
Yes, in the example migration file there is a bit more documentation. |
ok. thanks. last question, since libparallelproj is build from the parallelproj feedstock, I guess it should be:
|
No, this needs to be the package that should be pinned, not the feedstock. |
Ah ok. Good that I double checked. |
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 withlibparallelproj
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 stageThe text was updated successfully, but these errors were encountered: