conda-forge / conda-forge/awscli2-feedstock
[warning] failed package validation and/or copy for commit 64a70e467add886a5fceec1faf67468724fae047
- Dominant language
- No language data
- Stars
- 2
- Forks
- 6
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 20
Description
Hi @conda-forge/awscli2! 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](https://app.element.io/#/room/#conda-forge:matrix.org) or you can bump us right here.
output validation (is this output allowed for your feedstock?):
- **linux-64/awscli-2.13.10-py39hf3d152e_0.conda**: False
copied (did this output get copied to the production channel?):
- **linux-64/awscli-2.13.10-py39hf3d152e_0.conda**: False
error messages:
- output linux-64/awscli-2.13.10-py39hf3d152e_0.conda not allowed for conda-forge/awscli2-feedstock
To fix invalid outputs, you may need to manually add this feedstock to the feedstock-outputs map (did another feedstock already make this package?):
- https://github.com/conda-forge/feedstock-outputs
Contributor guide
Research direction
Start by rerendering the awscli2 feedstock, as the issue notes this usually fixes validation or copy failures. If the output remains invalid, inspect the feedstock-outputs map referenced in the issue and verify the listed linux-64 package is allowed; done means the output validates and copies to conda-forge.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100