Skip to content
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

readthedocs build failing: missing pkgs/main conda channel #2227

Closed
ctb opened this issue Aug 20, 2022 · 1 comment · Fixed by #2231
Closed

readthedocs build failing: missing pkgs/main conda channel #2227

ctb opened this issue Aug 20, 2022 · 1 comment · Fixed by #2231

Comments

@ctb
Copy link
Contributor

ctb commented Aug 20, 2022

we're getting the following error on readthedocs builds as of about 8 hours ago -

%  conda env create --quiet --name 2225 --file doc/environment.yml 
 Collecting package metadata: ...working... failed

UnavailableInvalidChannel: The channel is not accessible or is invalid.
  channel name: pkgs/main
  channel url: https://repo.anaconda.com/pkgs/main
  error code: 404

You will need to adjust your conda configuration to proceed.
Use `conda config --show channels` to view your configuration's current state,
and use `conda config --show-sources` to view config file locations.

while this channel is not in our doc/environment.yml it looks like it might be something added by RTD, based on free-associating from readthedocs/readthedocs.org#8059.

Reading https://server-docs.anaconda.com/en/latest/reference/troubleshooting.html, it appears that anaconda might be blocking the readthedocs build server from accessing that channel - possible reasons given, in order of likelihood, are -

The user has misconfigured their channels in their configuration (for example, the secure location where the token is stored was accidentally deleted (most common)

A firewall or other security device or system is preventing user access (second most common)

We are blocking their access because of a potential terms of service violation (third most common)

I'm not going to do anything more to troubleshoot it just yet, maybe it'll get fixed over the weekend or something...

@robelgeda
Copy link

Can confirm I see it too, good to know its wide spread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants