-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
several conda commands raise Response304ContentUnchanged() #8293
Comments
Sorry, we're having some trouble with our legacy metadata somehow. We're looking into it. You can avoid this by avoiding the "free" part of the default channel in your condarc:
|
@msarahan That did it, thanks for the quick reply! Do you want me to close this or keep it open? |
I am having the same issue, just one stupid question: |
Found it, thanks. |
We are running conda in a CI env. What's the command to update the default_channels in condarc? |
same here
|
I am getting this exact same issue. Multiple windows PCs. Miniconda works fine on Linux machines. Reinstallation of Anaconda3 did not help
|
We have identified the issue - repodata.json.bz2 did not match repodata.json, and also contained faulty metadata. We're uploading fixed metadata now. Please be patient. |
Should be fixed - closing this issue. Please file a new one if you see further issues. |
Hi there, thank you for your contribution to Conda! This issue has been automatically locked since it has not had recent activity after it was closed. Please open a new issue if needed. |
Current Behavior
Steps to Reproduce
Run some standard
conda
commands, for example:Expected Behavior
conda install <package>
,conda upgrade <package>
,conda create -n <some environment> <some package>
should work. That is,install
should download and install the requested package(s)upgrade
should upgrade the requested packages(s), andcreate
should create an environment with requested package(s).Environment Information
`conda info`
`conda config --show-sources`
`conda list --show-channel-urls`
The text was updated successfully, but these errors were encountered: