conda-forge / conda-forge/python-duckdb-feedstock
[warning] failed package validation and/or copy for commit b81a230aaca87865e20dc639d281c2a7222b267a
- Dominant language
- Shell
- Stars
- 13
- Forks
- 14
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 1
Description
Hi @conda-forge/python-duckdb! 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?):
- **noarch/duckdb-0.10.2-hd8ed1ab_1.conda**: False
copied (did this output get copied to the production channel?):
- **noarch/duckdb-0.10.2-hd8ed1ab_1.conda**: False
error messages:
- output noarch/duckdb-0.10.2-hd8ed1ab_1.conda not allowed for conda-forge/python-duckdb-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
Assessment
This issue has not been assessed yet.