-
Notifications
You must be signed in to change notification settings - Fork 220
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
R ICU dependency conflict not detected #1403
Comments
Just to say the bigger issue here is to enable both rpy2 and software from conda-forge to be installed safely into the same conda environment. But I realise that is tricky right now so I am comfortable with whatever resolution is appropriate for this issue right now. |
Hello, Having the same issue here: when upgrading from R-3.3.1 to R-3.3.2 Best regards, |
The only possible resolution, while |
Many thanks @mingwandroid |
conda-forge and conda-defaults are binary incompatible for now. See: ContinuumIO/anaconda-issues#1403 and https://groups.google.com/a/continuum.io/forum/#!topic/anaconda/myBjZaaAoDI
As described here, if a user installs rpy2 from the r channel, then installs any software from conda-forge that depends on ICU, then ICU will get upgraded to version 56 and r-base will get installed from conda-forge. After this, some parts of R run fine, but others generate an error regarding a missing ICU 54 library file (e.g., running the rpy2 test suite). This suggests that there is a dependency conflict somewhere that is not being caught by the conda installer, which ideally should raise a version conflict message rather than allow upgrade of ICU.
The text was updated successfully, but these errors were encountered: