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

[warning] failed package validation and/or copy for commit 845e24e2b8739ef13fee9f09f4649311c1b5ba04 #4412

Open
conda-forge-webservices bot opened this issue May 3, 2023 · 10 comments

Comments

@conda-forge-webservices
Copy link
Contributor

Hi @conda-forge/conda-forge-pinning! 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 gitter in the
community chat room or you can bump us right here.

output validation (is this output allowed for your feedstock?):

  • noarch/conda-forge-pinning-2023.05.03.14.47.14-hd8ed1ab_0.conda: True

copied (did this output get copied to the production channel?):

  • noarch/conda-forge-pinning-2023.05.03.14.47.14-hd8ed1ab_0.conda: False
@conda-forge-webservices
Copy link
Contributor Author

Hi @conda-forge/conda-forge-pinning! 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.

output validation (is this output allowed for your feedstock?):

  • noarch/conda-forge-pinning-2023.06.08.10.36.51-hd8ed1ab_0.conda: True

copied (did this output get copied to the production channel?):

  • noarch/conda-forge-pinning-2023.06.08.10.36.51-hd8ed1ab_0.conda: False

@h-vetinari
Copy link
Member

Closing this as obsolete

@conda-forge-webservices
Copy link
Contributor Author

Hi @conda-forge/conda-forge-pinning! 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:

  • invalid feedstock token

7 similar comments
@conda-forge-webservices
Copy link
Contributor Author

Hi @conda-forge/conda-forge-pinning! 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:

  • invalid feedstock token

@conda-forge-webservices
Copy link
Contributor Author

Hi @conda-forge/conda-forge-pinning! 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:

  • invalid feedstock token

@conda-forge-webservices
Copy link
Contributor Author

Hi @conda-forge/conda-forge-pinning! 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:

  • invalid feedstock token

@conda-forge-webservices
Copy link
Contributor Author

Hi @conda-forge/conda-forge-pinning! 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:

  • invalid feedstock token

@conda-forge-webservices
Copy link
Contributor Author

Hi @conda-forge/conda-forge-pinning! 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:

  • invalid feedstock token

@conda-forge-webservices
Copy link
Contributor Author

Hi @conda-forge/conda-forge-pinning! 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:

  • invalid feedstock token

@conda-forge-webservices
Copy link
Contributor Author

Hi @conda-forge/conda-forge-pinning! 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:

  • invalid feedstock token

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

No branches or pull requests

1 participant