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

[conda-forge-webservices]

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]

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]

Closing this as obsolete

[conda-forge-webservices]

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]

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]

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]

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]

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]

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]

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]

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]

Hi @conda-forge/conda-forge-pinning! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's packages 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 or your feedstock not having permissions to upload the given package.
Below we have put some information about the failure to help you debug it.

Common ways to fix this problem include:

• Retry the package build and upload by pushing an empty commit to the feedstock.
• Rerender the feedstock in a PR from a fork of the feedstock and merge.
• Request a feedstock token reset via our admin-requests repo.
• Request that any new packages be added to the allowed outputs for the feedstock
  via our admin-requests repo.
• In rare cases, the package name may change regularly in a well defined way (e.g., libllvm18, libllvm19, etc.).
  In this case, you can use our admin-requests repo
  to add a glob pattern that matches the new package name pattern. We use the Python fnmatch module syntax.
  Output packages that match these patterns will be automatically registered for your feedstock.

If you have any issues or questions, you can find us on Zulip in the
community channel or you can bump us right here.

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

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

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

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

[conda-forge-webservices]

Hi @conda-forge/conda-forge-pinning! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's packages 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 or your feedstock not having permissions to upload the given package.
Below we have put some information about the failure to help you debug it.

Common ways to fix this problem include:

• Retry the package build and upload by pushing an empty commit to the feedstock.
• Rerender the feedstock in a PR from a fork of the feedstock and merge.
• Request a feedstock token reset via our admin-requests repo.
• Request that any new packages be added to the allowed outputs for the feedstock
  via our admin-requests repo.
• In rare cases, the package name may change regularly in a well defined way (e.g., libllvm18, libllvm19, etc.).
  In this case, you can use our admin-requests repo
  to add a glob pattern that matches the new package name pattern. We use the Python fnmatch module syntax.
  Output packages that match these patterns will be automatically registered for your feedstock.

If you have any issues or questions, you can find us on Zulip in the
community channel or you can bump us right here.

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

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

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

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