-
Notifications
You must be signed in to change notification settings - Fork 57
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
disable auto_update_conda?: conflict conda versions when installing RCall.jl and PyCall.jl #242
Comments
Just notice that here is an option By default it is True, so the above 23.1.0 would always upgrade to 23.5.0. And the error Anyway, one workaround is to disable the auto-update of conda. So before building PyCall, I manually add the following line
to However, I do not know how I can insert such config before building PyCall and RCall in the AutoMerge task. Since those building procedures are before my package, I cannot configure them before their builds. Any ideas? Thanks! |
thank you so much for filing this issue - your suggestion to disable I shared my docker configuration here - maybe you can adapt it for your usecase |
@schlichtanders thanks for your feedback and share! Just pulled a request. |
I encountered the error in the AutoMege step when registering my package that depends on RCall.jl. Here is the pull request on the General repo and the action log info.
JuliaRegistries/General#86838
https://github.com/JuliaRegistries/General/actions/runs/5464785321/jobs/9947294633?pr=86838
I tried to reproduce the error locally to understand the logic. And I found that it should be related to the building order of
Conda.jl
,RCall.jl
,PyCall.jl
. Here are my testing results for different building order(I have deleted
~/.julia/conda
before each attempt to reinstall conda, since the culprit is the conda version)Specifically, after checking the build.log after building RCall.jl or PyCall.jl, both first install conda=23.1.0, and then update to be conda=23.5.0
I am quite confused why the order makes difference!
Although the simple workaround seems be to build RCall before PyCall, I am still trying to figure out how to implement it in the AutoMerge automated task.
(I noticed that building conda actually did not install conda, conda is installed until building PyCall or RCall.)
Can anyone give some advices/hints? Thanks. Or is there any simple way to avoid the conflict conda versions?
The text was updated successfully, but these errors were encountered: