-
Notifications
You must be signed in to change notification settings - Fork 423
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
ValueError: Incompatible component merge: mpi_openmpi_* #4498
Comments
I had the same problem with |
@mguijarr It's working! Thanks a lot! So many snakes to use instead of conda :) |
I don't think this should be closed, since it is not solved with conda itself. |
Reopened ;) |
I was able to fix it by forcing higher numpy version (>=1.17) in my |
Trying to fix build issues as mentioned here -> conda/conda-build#4498 (comment)
See a possible workaround in conda/conda#11442 (comment). |
I accidentally rediscovered this solution after running into a case that was not solved by the workaround I posted in the last comment. As of writing, it looks like building any package that has conda-forge This issue can be reproduced by trying to build the following trivial
It seems that some change within the conda-forge channel (probably the addition of certain builds?) has broken recipes that were previously working. I think this is really a |
Any progress on this? I'm hitting this regularly and have to use ValueError: Incompatible component merge:
- '*mpich*'
- 'mpi_mpich_*' $ cat meta.yaml
{% set name = "bitsandbytes" %}
{% set version = "0.39.0" %}
package:
name: "{{ name|lower }}"
version: "{{ version }}"
build:
number: 0
requirements:
host:
- pip
- python {{ PY_VER }}*,>=3.6
- absl-py
- nltk
- numpy
- six>=1.14
run:
- python {{ PY_VER }}*,>=3.6
- absl-py
- nltk
- numpy
- six>=1.14
test:
imports:
- bitsandbytes
$ cat build.sh
pip install bitsandbytes==0.39.0 |
@chebee7i Did you try using |
That does indeed seem to fix the issue. Very weird that we need it, since it should be picking up something much more recent than 1.17 even. |
Summary: Based on comments in conda/conda-build#4498 Pull Request resolved: #2896 Reviewed By: mdouze Differential Revision: D46802512 Pulled By: algoriddle fbshipit-source-id: 7449b2f0db08fdd793770a44afb659d7ac28e3cd
Restricting to
Switching to |
Still hitting this issue with numpy 1.22. |
Summary: Based on comments in conda/conda-build#4498 Pull Request resolved: facebookresearch#2896 Reviewed By: mdouze Differential Revision: D46802512 Pulled By: algoriddle fbshipit-source-id: 7449b2f0db08fdd793770a44afb659d7ac28e3cd
Hi there, thank you for your contribution! This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs. If you would like this issue to remain open please:
NOTE: If this issue was closed prematurely, please leave a comment. Thanks! |
I'd appreciate it if stale bots didn't create work for people. Still an issue, fix is known: conda/conda#11612
Interestingly, mamba doesn't appear to have this problem. |
Actual Behavior
Hi,
I'm trying to build R package which I would like to upload to anaconda. I am following the instructions from here: https://stackoverflow.com/questions/52061664/install-r-package-from-github-using-conda
conda skeleton cran https://github.com/pawel125/clonalityParsers
works fine, although I have to correct the names of two packages:r-genomeinfodb -> bioconductor-genomeinfodb and r-plyranges -> bioconductor-plyranges
Unfortunatelly
conda build --R=4.2.0 r-clonalityparsers
results in the following error:Could you help me to solve this issue?
Thanks!
Expected Behavior
Conda builds the package.
Steps to Reproduce
Replace package names in meta.yaml:
r-genomeinfodb -> bioconductor-genomeinfodb
r-plyranges -> bioconductor-plyranges
Output of conda info
I am using conda version 4.12.0
The text was updated successfully, but these errors were encountered: