-
Notifications
You must be signed in to change notification settings - Fork 34
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
conda installation broken again with error installing cachetools-2.1.0-py_0
#511
Comments
This makes it fairly clear that it is time to upgrade the python dependencies, and I am not opposed to doing so, but I want to have reliable tests in place first so that I don't regress my own code. |
This issue will track the temporary workarounds to get the tests to pass again before we upgrade the dependencies. |
Using
|
Try 1: upgrade google-authversion 1.7.0 updated the cachetools dependency Still fails
Try 2: create an empty environment before installing all packagessince the secondary error is related to a FileNotFound for still fails
although the file clearly exists, is executable, and is not a symlink
Try 3: download the correct version from conda-forge manually and install itThat got rid of that error, but now the geojson package is failing
|
After going through and manually downloading every package that I was broken, I got this to work. The full list is:
All the other modules, even from conda-forge, are installed correctly. |
To workaround e-mission/e-mission-docs#511 The solution is in e-mission/e-mission-docs#511 (comment)
Fixed by #729 |
By using `source/setup.sh` instead of using conda directly. Corresponds to e-mission/e-mission-docs#511
This will allow us to catch bitrotted changes like e-mission/e-mission-docs#513 or e-mission/e-mission-docs#511 and make it easier for people who don't want to use docker to install
This should avoid weird issues caused by bitrotted miniconda versions similar to e-mission/e-mission-docs#511 or e-mission/e-mission-docs#513 If such bitrotting happens, we need to upgrade the packages, but at least we will know that we need to, and people won't have unpleasant surprises when they try to install manually. Apparently, some people prefer to install manually e-mission/e-mission-docs#513
This is very similar to the travis.yml, but it is in Github actions, so it can run on all PRs to the repo, not just mine. Also includes a weekly scheduled run + runs on various ubuntu OSes to catch any bitrotting similar to e-mission/e-mission-docs#511 or e-mission/e-mission-docs#513
To workaround e-mission/e-mission-docs#511 The solution is in e-mission/e-mission-docs#511 (comment)
This will allow us to catch bitrotted changes like e-mission/e-mission-docs#513 or e-mission/e-mission-docs#511 and make it easier for people who don't want to use docker to install
This should avoid weird issues caused by bitrotted miniconda versions similar to e-mission/e-mission-docs#511 or e-mission/e-mission-docs#513 If such bitrotting happens, we need to upgrade the packages, but at least we will know that we need to, and people won't have unpleasant surprises when they try to install manually. Apparently, some people prefer to install manually e-mission/e-mission-docs#513
This is very similar to the travis.yml, but it is in Github actions, so it can run on all PRs to the repo, not just mine. Also includes a weekly scheduled run + runs on various ubuntu OSes to catch any bitrotting similar to e-mission/e-mission-docs#511 or e-mission/e-mission-docs#513
This appears to be a regression in the past few days. When I experimented with the dev builds for docker-compose (around e-mission/e-mission-docker@c66f1c8), everything worked. Then, when I started testing using Travis CI, around
Thu Mar 12 23:15:25 2020
), I started getting the error.There were no source code changes in this time, and no reason why this should have regressed. This is a conda issue, so I have filed conda/conda#9761
I am very disturbed about conda's dependency checking bitrotting, since the whole point of using conda was to avoid getting sucked into dependency hell.
The text was updated successfully, but these errors were encountered: