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

Failure in conda build process, missing noarch/repodata.json #3114

Closed
marcelotrevisani opened this issue Sep 6, 2018 · 10 comments · Fixed by #3117 or #3120
Closed

Failure in conda build process, missing noarch/repodata.json #3114

marcelotrevisani opened this issue Sep 6, 2018 · 10 comments · Fixed by #3117 or #3120
Labels
locked [bot] locked due to inactivity

Comments

@marcelotrevisani
Copy link
Member

marcelotrevisani commented Sep 6, 2018

I have seeing some errors in conda-forge after the new conda-build release.

The error is regarding a missing noarch/repodata.json.

It's possible to see the conda version and also the process in this link:

https://circleci.com/gh/conda-forge/staged-recipes/30232?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

There are at least 3 packages which are failing in conda-forge, like:
conda-forge/staged-recipes#6587
conda-forge/staged-recipes#6623
conda-forge/staged-recipes#6624

And there is an open issue in conda-forge regarding that:
conda-forge/staged-recipes#6587

@marcelotrevisani
Copy link
Member Author

Quoting @mbargull

@marcelotrevisani, I didn't take an in depth look at it, but it's possibly a bug introduced with the index changes in conda-build 3.14. If you don't find any other explanation, please raise a conda-build issue.

@marcelotrevisani
Copy link
Member Author

cc: @nicoddemus

@msarahan
Copy link
Contributor

msarahan commented Sep 6, 2018

It could be a problem in the new conda index, but conda index is not used by anaconda.org at all. This seems potentially like an anaconda.org problem, which may instead be tied to a recent re-deployment that we had to do because disks were full.

@mbargull
Copy link
Member

mbargull commented Sep 6, 2018

It's not anaconda.org, it's not finding the local build channel. (Though I have no idea why this gives an HTTP error 😕.)

@msarahan
Copy link
Contributor

msarahan commented Sep 6, 2018

I looked at the error more, and it's definitely a conda-build problem. The 404 is happening on the local channel. I'll take a look at this ASAP.

@msarahan
Copy link
Contributor

msarahan commented Sep 6, 2018

This is happening because update_index was changed to operate on whole channels, not on subdirs. https://github.com/conda-forge/staged-recipes/blob/master/.ci_support/build_all.py#L34

We probably need to fix conda-smithy in the long-term, but for the short-term, I'll put in a fix to conda-build and a deprecation warning.

Sorry for the unintentional breaking change.

@marcelotrevisani
Copy link
Member Author

@msarahan
Copy link
Contributor

msarahan commented Sep 6, 2018

hmmm.... it is taking the new code path I put in:

The update_index function has changed to index all subdirs at once.  You're pointing it at a single subdir.  Please update your code to point it at the channel root, rather than a subdir.

I'll have to try again.

@marcelotrevisani
Copy link
Member Author

Thanks @msarahan to fix this! :)

@github-actions
Copy link

Hi there, thank you for your contribution!

This issue has been automatically locked because it has not had recent activity after being closed.

Please open a new issue if needed.

Thanks!

@github-actions github-actions bot added the locked [bot] locked due to inactivity label Mar 14, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity
Projects
None yet
3 participants