search

regro / conda-metachannel

like a conda-metapackage but for channels!
MIT License
69 stars 4 forks source link

conda 4.7 causes a 500 error with the new repo.json #30

Open s22chan opened 5 years ago

s22chan commented 5 years ago 
Collecting package metadata (current_repodata.json): failed

CondaHTTPError: HTTP 500 CONNECTION FAILED for url <https://metachannel.conda-forge.org/conda-forge/--max-build-no,llvmdev,ncurses/osx-64/current_repodata.json>
Elapsed: 00:00.078733
CF-RAY: 4f0149b3ad57caa8-YYZ
scopatz commented 5 years ago

I think #29 fixed this. @mariusvniekerk - do we need to do a release?

mariusvniekerk commented 5 years ago

@scopatz yeah, probably

scopatz commented 5 years ago

0.1.1 released

alienzj commented 5 years ago 
Collecting package metadata (current_repodata.json): failed

CondaHTTPError: HTTP 500 CONNECTION FAILED for url <https://metachannel.conda-forge.org/defaults,alienzj,knights-lab,pytorch,bioconda,conda-forge/python,perl,r,pyani,--max-build-no/linux-64/current_repodata.json>
Elapsed: 00:03.009613
CF-RAY: 507918b4aee8a5a0-NRT

A remote server error occurred when trying to retrieve this URL.

A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to
fulfill a valid request.  The problem may be spurious, and will resolve itself if you
try your request again.  If the problem persists, consider notifying the maintainer
of the remote server.
alienzj commented 5 years ago

@scopatz Hello, Anthony, I still have meet HTTP Error.

mariusvniekerk commented 5 years ago

I don't think all of those channels have a current_repodata....

scopatz commented 5 years ago

I am still seeing this

alienzj commented 5 years ago

I am still seeing this