Closed greglandrum closed 1 year ago
Seems some CI tests I run got me the same issue. Saw it occurring also for rdkit-2022.03.2 (py39h89e00b9_0). In my case it only happened for ubtuntu, not macOS or windows (see CI results: https://github.com/matchms/matchms/actions/runs/3299894916/jobs/5453884303). Right now I am not sure how to fix it (other than skipping that combination or fixing rdkit versions).
Do we need to mark the affected packages as broken?
@jaimergp If that's straightforward to do, I think that would make sense.
See here @greglandrum:
https://conda-forge.org/docs/maintainer/updating_pkgs.html#removing-broken-packages
Any ideas how this happens? I skimmed through the build scripts and nothing stuck out as particularly obvious to me
What is the value of SP_DIR
in the build script?
and PREFIX
?
They are probably
Python's site-packages location. Build prefix to which the build script should install.
https://docs.conda.io/projects/conda-build/en/latest/user-guide/environment-variables.html
Fixed by #121
Solution to issue cannot be found in the documentation.
Issue
If I create a new environment with python 3.9 and the rdkit:
it looks like the RDKit isn't installed:
even though conda says it is:
and, in fact, there's no package in the right place:
instead there's something in python3.10/site-packages:
Looks like
xcbgen
has the same problem.Here's the original RDKit bug report, from @jrsacher: https://github.com/rdkit/rdkit/issues/5626
Installed packages
Environment info