conda fails to install python=36 (verification error)
See original GitHub issueOn an Ubuntu 16.04 system which had previously had litex-buildenv
installed, updating to the latest commit (52f75717ac6) which switches to python-36
results in a system that:
-
Fails
scripts/enter-env.sh
becausepython
3.6 is missing; and -
Fails
scripts/download-env.sh
because conda fails to installpython
3.6 due toCondaVerificationError
on seemingly every single python file, egCondaVerificationError: The package for chardet located at /src/fpga-miniconf/litex-buildenv/build/conda/pkgs/chardet-3.0.4-py36h0f667ec_1 appears to be corrupted. The path ‘lib/python3.6/site-packages/chardet/pycache/init.cpython-36.pyc’ specified in the package manifest cannot be found.
(see also gist with full output).
From some reading (eg, https://github.com/conda/conda-build/issues/1301, https://github.com/conda/conda/issues/6033, https://github.com/conda-forge/python-feedstock/issues/70) my current guess is that perhaps this was an issue with an older version of conda
, and then the bug got fixed, and everyone moved on. However it appears that scripts/download-env.sh
will only ever update conda
on first installation (from miniconda
) and then after that assumes that the installed version will work perfectly; see
(and note the conda ... update
is guarded by if no bin/conda
exists, so it’ll only happen once).
I’m about to try manually doing conda update conda
and see if that is sufficient to fix the issue. But am making an issue now as a record in case others run into the same issue…
Ewen
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (6 by maintainers)
After concluding that reinstalling the
conda
environment was going to be quicker, I did:and it seemed to work perfectly. I assume the
python=3.5
topython=3.6
upgrade process isn’t very well tested. I did briefly try to find a combination ofconda
packages I could remove to avoid the.pyc
complaints… but a bunch that I tried wereconda
dependencies, and unsurprisingly conda is unwilling to remove itself, so I gave up on that approach.FTR, output of reinstalling after
mv build/conda build/conda-3.5
. At least with a fast network connection it took only a few minutes – way less time than I spent trying to make it work without doing that 😃 (And it might have been faster if I had, eg, found a way to saveconda/pkgs/
or similar.)Ewen
In case it helps, I have conda 4.4.7 installed, using Python 3.5, along with these packages:
all of which are notably the py35 versions rather than the py36 versions…
Ewen