Closed billytcl closed 3 years ago
I think your conda base env is too old (conda/4.3.30, CPython/2.7.13). Could you please try updating both conda
and python
in your base env, and then retry the installation? The =1.2.2.5
spec is coming from a recent repo metadata patch (https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/141), and it looks like the patcher needs Python 3 to work.
I don’t have permissions to change the base Python or conda on our server. Is there a way around this?
On Sun, May 9, 2021 at 12:06 AM Leo Fang @.***> wrote:
I think your conda base env is too old (conda/4.3.30, CPython/2.7.13). Could you please try updating both conda and python in your base env, and then retry the installation? The =1.2.2.5 spec is coming from a recent repo metadata patch ( conda-forge/conda-forge-repodata-patches-feedstock#141 https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/141), and it looks like the patcher needs Python 3 to work.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/conda-forge/cupy-feedstock/issues/127#issuecomment-835719690, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACPHYT6ATRSYEX76Q6OEMZDTMYX55ANCNFSM44OTTAUA .
@conda-forge/core Any advice?
@billytcl You can have your own conda installation anywhere you have write access to using one of the miniforge installers. That said I would encourage you to ask your sysadmin to update conda as 4.3 is very old and is likely to have other issues.
@leofang I think you can fix this properly cutensor =1.2.2.5
with cutensor 1.2.2.5.*
in the patch generation script to keep support for these old conda versions.
it looks like the patcher needs Python 3 to work.
The patcher isn't ran by the client so it doesn't matter what version they're using. It's ran once on the server side as part of the generation process for the repodata.json
blob.
Thanks for clarification @chrisburr.
@billytcl Could you please try installing a fresh conda to somewhere you have write access (say to your home directory) and avoid using the outdated base env, and then retry?
@billytcl Any luck?
@billytcl I am closing this issue due to no response. Feel free to reopen if you install a fresh conda in the user space but still have problems.
Issue: I get a mysterious Invalid spec error when trying to install from from conda-forge channel $ conda install -v -c conda-forge cupy Fetching package metadata ............. An unexpected error has occurred. Please consider posting the following information to the conda GitHub issue tracker at:
Current conda install:
$ /mnt/ix2/Experimental_tools/bonito_suzuki/bin/conda install -v -c conda-forge cupy
Environment (
conda list
):Details about
conda
and system (conda info
):