Skip to content

conda version used at RTD contains bug -- newer version available #3150

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

Closed
wkerzendorf opened this issue Oct 6, 2017 · 11 comments
Closed

conda version used at RTD contains bug -- newer version available #3150

wkerzendorf opened this issue Oct 6, 2017 · 11 comments
Labels
Bug A bug

Comments

@wkerzendorf
Copy link

Details

http://tardis.readthedocs.io/en/latest/
https://readthedocs.org/projects/tardis/builds/6084573/
rtd user wkerzendorf

Expected Result

We want to use the new conda build system to install our requirements.

Actual Result

The conda version used at RTD is 4.3.11 - the bug that we encounter is
ValidationError: Value for sha256 cannot be None

that should be fixed in 4.3.14 according to conda/conda#5278

@wkerzendorf
Copy link
Author

@RichardLitt this is the problem - which I think is fixed in newer conda versions. thanks for the help

@RichardLitt RichardLitt added the Bug A bug label Oct 6, 2017
@wkerzendorf
Copy link
Author

Is there any ETA for an update of conda on RTD?

@RichardLitt
Copy link
Member

I'm trying to locate where the conda version is specified in the codebase, and I can't. @wkerzendorf how do you know that it is version 4.3.11?

@wkerzendorf
Copy link
Author

@RichardLitt I'm not sure what you mean. The conda version used by rtd is 4.3.11 (and you can see that in the log). This conda version has problems resulting in the observed error. The easiest would be to update rtd to a newer conda version. Does that help?

@RichardLitt
Copy link
Member

@wkerzendorf Cool. I was trying to see if we could make a PR, but it sounds like this is a support issue. Labelling it appropriately.

@RichardLitt RichardLitt added the Support Support question label Oct 9, 2017
@wkerzendorf
Copy link
Author

@RichardLitt thank you for your help. If there are things we can help with (like testing) please let us know.

@humitos
Copy link
Member

humitos commented Oct 11, 2017

The conda version is specified in the docker build image: https://github.com/rtfd/readthedocs-docker-images/blob/master/Dockerfile#L54

@wkerzendorf
Copy link
Author

@agjohnson how long until our fix trickles through to the actual docker images. I just built right now and it is still version 4.3.11.

@agjohnson
Copy link
Contributor

I've just deployed the new images to our build servers. You can try a build now and should get the correct version of conda.

@agjohnson
Copy link
Contributor

I haven't heard anything back to the contrary, so I'll close this. Feel free to reopen if the new build images didn't fix this problem.

I added automated tracking of the conda version releases through our CI:
https://github.com/rtfd/readthedocs-docker-images/blob/master/tests/test_dependencies.py

So we'll get CI failures when conda releases new versions. Hopefully this helps us keep more up to date.

@agjohnson agjohnson removed the Support Support question label Oct 28, 2017
@wkerzendorf
Copy link
Author

@RichardLitt @agjohnson works like a charm - thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A bug
Projects
None yet
Development

No branches or pull requests

4 participants