-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
[warning] failed package validation and/or copy for commit f0bdf44b8fca03de9d99c256fe39f97d61c47d8a #4
Comments
see #5 |
Hi @conda-forge/jupyterlab-github! This is the friendly automated conda-forge-webservice! It appears that one or more of your feedstock's outputs did not copy from the This failure can happen for a lot of reasons, including an outdated feedstock Rerendering the feedstock will usually fix these problems. If you have any issues or questions, you can find us on Element in the error messages:
|
1 similar comment
Hi @conda-forge/jupyterlab-github! This is the friendly automated conda-forge-webservice! It appears that one or more of your feedstock's outputs did not copy from the This failure can happen for a lot of reasons, including an outdated feedstock Rerendering the feedstock will usually fix these problems. If you have any issues or questions, you can find us on Element in the error messages:
|
@conda-forge/core what's the procedure for getting this fixed? |
Can you try requesting a token-reset for this feedstock under https://github.com/conda-forge/admin-requests/? |
Hi @conda-forge/jupyterlab-github! This is the friendly automated conda-forge-webservice! It appears that one or more of your feedstock's outputs did not copy from the This failure can happen for a lot of reasons, including an outdated feedstock Rerendering the feedstock will usually fix these problems. If you have any issues or questions, you can find us on Element in the error messages:
|
2 similar comments
Hi @conda-forge/jupyterlab-github! This is the friendly automated conda-forge-webservice! It appears that one or more of your feedstock's outputs did not copy from the This failure can happen for a lot of reasons, including an outdated feedstock Rerendering the feedstock will usually fix these problems. If you have any issues or questions, you can find us on Element in the error messages:
|
Hi @conda-forge/jupyterlab-github! This is the friendly automated conda-forge-webservice! It appears that one or more of your feedstock's outputs did not copy from the This failure can happen for a lot of reasons, including an outdated feedstock Rerendering the feedstock will usually fix these problems. If you have any issues or questions, you can find us on Element in the error messages:
|
Reset Azure only with PR ( conda-forge/admin-requests#784 ). Travis was stuck, but we don't use that here Starting a new build Closing assuming that will fix it. Bot will reopen if not |
Package are now up! 🚀 |
Thanks for bringing that one home ❤️ |
Hi @conda-forge/jupyterlab-github! This is the friendly automated conda-forge-webservice!
It appears that one or more of your feedstock's outputs did not copy from the
staging channel (cf-staging) to the production channel (conda-forge). :(
This failure can happen for a lot of reasons, including an outdated feedstock
token. Below we have put some information about the failure to help you debug it.
Rerendering the feedstock will usually fix these problems.
If you have any issues or questions, you can find us on Element in the
community channel or you can bump us right here.
error messages:
The text was updated successfully, but these errors were encountered: