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

[conda-forge-webservices[bot]]

Hi @conda-forge/dartsim! 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, please submit a PR updating our list of feedstocks with allowed glob patterns. 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 Element in the community channel or you can bump us right here.

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

• osx-arm64/dartsim-cpp-6.14.4-h1793c38_5.conda: False

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

• osx-arm64/dartsim-cpp-6.14.4-h1793c38_5.conda: False

error messages:

• output osx-arm64/dartsim-cpp-6.14.4-h1793c38_5.conda not allowed for conda-forge/dartsim-feedstock

To fix package package output validation errors, follow the instructions above to addnew package outputs to your feedstock or to add your feedstock+packages to the allow list for automatic registration.

[conda-forge-webservices[bot]]

Hi @conda-forge/dartsim! 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, please submit a PR updating our list of feedstocks with allowed glob patterns. 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 Element in the community channel or you can bump us right here.

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

• osx-64/dartsim-cpp-6.14.4-hb79efbb_5.conda: False

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

• osx-64/dartsim-cpp-6.14.4-hb79efbb_5.conda: False

error messages:

• output osx-64/dartsim-cpp-6.14.4-hb79efbb_5.conda not allowed for conda-forge/dartsim-feedstock

To fix package package output validation errors, follow the instructions above to addnew package outputs to your feedstock or to add your feedstock+packages to the allow list for automatic registration.

[conda-forge-webservices[bot]]

Hi @conda-forge/dartsim! 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, please submit a PR updating our list of feedstocks with allowed glob patterns. 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 Element in the community channel or you can bump us right here.

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

• linux-aarch64/dartsim-cpp-6.14.4-hbb8f0f2_5.conda: False

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

• linux-aarch64/dartsim-cpp-6.14.4-hbb8f0f2_5.conda: False

error messages:

• output linux-aarch64/dartsim-cpp-6.14.4-hbb8f0f2_5.conda not allowed for conda-forge/dartsim-feedstock

To fix package package output validation errors, follow the instructions above to addnew package outputs to your feedstock or to add your feedstock+packages to the allow list for automatic registration.

[conda-forge-webservices[bot]]

Hi @conda-forge/dartsim! 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, please submit a PR updating our list of feedstocks with allowed glob patterns. 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 Element in the community channel or you can bump us right here.

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

• linux-ppc64le/dartsim-cpp-6.14.4-hcf611e8_5.conda: False

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

• linux-ppc64le/dartsim-cpp-6.14.4-hcf611e8_5.conda: False

error messages:

• output linux-ppc64le/dartsim-cpp-6.14.4-hcf611e8_5.conda not allowed for conda-forge/dartsim-feedstock

To fix package package output validation errors, follow the instructions above to addnew package outputs to your feedstock or to add your feedstock+packages to the allow list for automatic registration.

[conda-forge-webservices[bot]]

Hi @conda-forge/dartsim! 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, please submit a PR updating our list of feedstocks with allowed glob patterns. 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 Element in the community channel or you can bump us right here.

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

• win-64/dartsim-cpp-6.14.4-h1190057_5.conda: False

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

• win-64/dartsim-cpp-6.14.4-h1190057_5.conda: False

error messages:

• output win-64/dartsim-cpp-6.14.4-h1190057_5.conda not allowed for conda-forge/dartsim-feedstock

To fix package package output validation errors, follow the instructions above to addnew package outputs to your feedstock or to add your feedstock+packages to the allow list for automatic registration.

[conda-forge-webservices[bot]]

Hi @conda-forge/dartsim! 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, please submit a PR updating our list of feedstocks with allowed glob patterns. 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 Element in the community channel or you can bump us right here.

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

• osx-arm64/dartsim-cpp-6.14.5-h1793c38_0.conda: False

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

• osx-arm64/dartsim-cpp-6.14.5-h1793c38_0.conda: False

error messages:

• output osx-arm64/dartsim-cpp-6.14.5-h1793c38_0.conda not allowed for conda-forge/dartsim-feedstock

To fix package package output validation errors, follow the instructions above to add new package outputs to your feedstock or to add your feedstock+packages to the allow list for automatic registration.

[conda-forge-webservices[bot]]

Hi @conda-forge/dartsim! 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, please submit a PR updating our list of feedstocks with allowed glob patterns. 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 Element in the community channel or you can bump us right here.

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

• osx-64/dartsim-cpp-6.14.5-hb79efbb_0.conda: False

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

• osx-64/dartsim-cpp-6.14.5-hb79efbb_0.conda: False

error messages:

• output osx-64/dartsim-cpp-6.14.5-hb79efbb_0.conda not allowed for conda-forge/dartsim-feedstock

To fix package package output validation errors, follow the instructions above to add new package outputs to your feedstock or to add your feedstock+packages to the allow list for automatic registration.

[conda-forge-webservices[bot]]

Hi @conda-forge/dartsim! 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, please submit a PR updating our list of feedstocks with allowed glob patterns. 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 Element in the community channel or you can bump us right here.

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

• linux-ppc64le/dartsim-cpp-6.14.5-hcf611e8_0.conda: False

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

• linux-ppc64le/dartsim-cpp-6.14.5-hcf611e8_0.conda: False

error messages:

• output linux-ppc64le/dartsim-cpp-6.14.5-hcf611e8_0.conda not allowed for conda-forge/dartsim-feedstock

To fix package package output validation errors, follow the instructions above to add new package outputs to your feedstock or to add your feedstock+packages to the allow list for automatic registration.

[conda-forge-webservices[bot]]

Hi @conda-forge/dartsim! 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, please submit a PR updating our list of feedstocks with allowed glob patterns. 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 Element in the community channel or you can bump us right here.

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

• osx-arm64/dartsim-cpp-6.14.5-h1793c38_1.conda: False

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

• osx-arm64/dartsim-cpp-6.14.5-h1793c38_1.conda: False

error messages:

• output osx-arm64/dartsim-cpp-6.14.5-h1793c38_1.conda not allowed for conda-forge/dartsim-feedstock

To fix package package output validation errors, follow the instructions above to add new package outputs to your feedstock or to add your feedstock+packages to the allow list for automatic registration.

[conda-forge-webservices[bot]]

Hi @conda-forge/dartsim! 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, please submit a PR updating our list of feedstocks with allowed glob patterns. 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 Element in the community channel or you can bump us right here.

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

• osx-64/dartsim-cpp-6.14.5-hb79efbb_1.conda: False

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

• osx-64/dartsim-cpp-6.14.5-hb79efbb_1.conda: False

error messages:

• output osx-64/dartsim-cpp-6.14.5-hb79efbb_1.conda not allowed for conda-forge/dartsim-feedstock

To fix package package output validation errors, follow the instructions above to add new package outputs to your feedstock or to add your feedstock+packages to the allow list for automatic registration.

[conda-forge-webservices[bot]]

Hi @conda-forge/dartsim! 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, please submit a PR updating our list of feedstocks with allowed glob patterns. 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 Element in the community channel or you can bump us right here.

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

• linux-64/dartpy-6.14.4-py311hc05e171_5.conda: False
• linux-64/dartpy-6.14.4-py39h62e4e38_5.conda: False
• linux-64/dartpy-6.14.4-py312hff1b3f8_5.conda: False
• linux-64/dartsim-cpp-6.14.4-h0ed660e_5.conda: False
• linux-64/dartpy-6.14.4-py310hb5b2f5b_5.conda: False

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

• linux-64/dartpy-6.14.4-py311hc05e171_5.conda: False
• linux-64/dartpy-6.14.4-py39h62e4e38_5.conda: False
• linux-64/dartpy-6.14.4-py312hff1b3f8_5.conda: False
• linux-64/dartsim-cpp-6.14.4-h0ed660e_5.conda: False
• linux-64/dartpy-6.14.4-py310hb5b2f5b_5.conda: False

error messages:

• output linux-64/dartpy-6.14.4-py311hc05e171_5.conda not allowed for conda-forge/dartsim-feedstock - output linux-64/dartpy-6.14.4-py39h62e4e38_5.conda not allowed for conda-forge/dartsim-feedstock - output linux-64/dartpy-6.14.4-py312hff1b3f8_5.conda not allowed for conda-forge/dartsim-feedstock - output linux-64/dartsim-cpp-6.14.4-h0ed660e_5.conda not allowed for conda-forge/dartsim-feedstock - output linux-64/dartpy-6.14.4-py310hb5b2f5b_5.conda not allowed for conda-forge/dartsim-feedstock

To fix package package output validation errors, follow the instructions above to add new package outputs to your feedstock or to add your feedstock+packages to the allow list for automatic registration.

[conda-forge-webservices[bot]]

Hi @conda-forge/dartsim! 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, please submit a PR updating our list of feedstocks with allowed glob patterns. 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 Element in the community channel or you can bump us right here.

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

• linux-ppc64le/dartsim-cpp-6.14.5-hcf611e8_1.conda: False

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

• linux-ppc64le/dartsim-cpp-6.14.5-hcf611e8_1.conda: False

error messages:

• output linux-ppc64le/dartsim-cpp-6.14.5-hcf611e8_1.conda not allowed for conda-forge/dartsim-feedstock

To fix package package output validation errors, follow the instructions above to add new package outputs to your feedstock or to add your feedstock+packages to the allow list for automatic registration.

[conda-forge-webservices[bot]]

Hi @conda-forge/dartsim! 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, please submit a PR updating our list of feedstocks with allowed glob patterns. 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 Element in the community channel or you can bump us right here.

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

• linux-aarch64/dartsim-cpp-6.14.5-hbb8f0f2_0.conda: False

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

• linux-aarch64/dartsim-cpp-6.14.5-hbb8f0f2_0.conda: False

error messages:

• output linux-aarch64/dartsim-cpp-6.14.5-hbb8f0f2_0.conda not allowed for conda-forge/dartsim-feedstock

To fix package package output validation errors, follow the instructions above to add new package outputs to your feedstock or to add your feedstock+packages to the allow list for automatic registration.

[conda-forge-webservices[bot]]

Hi @conda-forge/dartsim! 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, please submit a PR updating our list of feedstocks with allowed glob patterns. 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 Element in the community channel or you can bump us right here.

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

• linux-aarch64/dartsim-cpp-6.14.5-hbb8f0f2_1.conda: False

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

• linux-aarch64/dartsim-cpp-6.14.5-hbb8f0f2_1.conda: False

error messages:

• output linux-aarch64/dartsim-cpp-6.14.5-hbb8f0f2_1.conda not allowed for conda-forge/dartsim-feedstock

To fix package package output validation errors, follow the instructions above to add new package outputs to your feedstock or to add your feedstock+packages to the allow list for automatic registration.

[conda-forge-webservices[bot]]

Hi @conda-forge/dartsim! 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, please submit a PR updating our list of feedstocks with allowed glob patterns. 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 Element in the community channel or you can bump us right here.

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

• win-64/dartsim-cpp-6.14.5-h1190057_0.conda: False

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

• win-64/dartsim-cpp-6.14.5-h1190057_0.conda: False

error messages:

• output win-64/dartsim-cpp-6.14.5-h1190057_0.conda not allowed for conda-forge/dartsim-feedstock

To fix package package output validation errors, follow the instructions above to add new package outputs to your feedstock or to add your feedstock+packages to the allow list for automatic registration.

[conda-forge-webservices[bot]]

Hi @conda-forge/dartsim! 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, please submit a PR updating our list of feedstocks with allowed glob patterns. 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 Element in the community channel or you can bump us right here.

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

• win-64/dartsim-cpp-6.14.5-h1190057_1.conda: False

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

• win-64/dartsim-cpp-6.14.5-h1190057_1.conda: False

error messages:

• output win-64/dartsim-cpp-6.14.5-h1190057_1.conda not allowed for conda-forge/dartsim-feedstock

To fix package package output validation errors, follow the instructions above to add new package outputs to your feedstock or to add your feedstock+packages to the allow list for automatic registration.

[conda-forge-webservices[bot]]

Hi @conda-forge/dartsim! 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, please submit a PR updating our list of feedstocks with allowed glob patterns. 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 Element in the community channel or you can bump us right here.

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

• linux-64/dartpy-6.14.5-py310hb5b2f5b_0.conda: False
• linux-64/dartpy-6.14.5-py39h62e4e38_0.conda: False
• linux-64/dartpy-6.14.5-py312hff1b3f8_0.conda: False
• linux-64/dartsim-cpp-6.14.5-h0ed660e_0.conda: False
• linux-64/dartpy-6.14.5-py311hc05e171_0.conda: False

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

• linux-64/dartpy-6.14.5-py310hb5b2f5b_0.conda: False
• linux-64/dartpy-6.14.5-py39h62e4e38_0.conda: False
• linux-64/dartpy-6.14.5-py312hff1b3f8_0.conda: False
• linux-64/dartsim-cpp-6.14.5-h0ed660e_0.conda: False
• linux-64/dartpy-6.14.5-py311hc05e171_0.conda: False

error messages:

• output linux-64/dartpy-6.14.5-py310hb5b2f5b_0.conda not allowed for conda-forge/dartsim-feedstock - output linux-64/dartpy-6.14.5-py39h62e4e38_0.conda not allowed for conda-forge/dartsim-feedstock - output linux-64/dartpy-6.14.5-py312hff1b3f8_0.conda not allowed for conda-forge/dartsim-feedstock - output linux-64/dartsim-cpp-6.14.5-h0ed660e_0.conda not allowed for conda-forge/dartsim-feedstock - output linux-64/dartpy-6.14.5-py311hc05e171_0.conda not allowed for conda-forge/dartsim-feedstock

To fix package package output validation errors, follow the instructions above to add new package outputs to your feedstock or to add your feedstock+packages to the allow list for automatic registration.

[traversaro]

@jslee02 I guess we need to add dartpy and dartsim-cpp to the allowed outputs for this feedstock following https://github.com/conda-forge/admin-requests?tab=readme-ov-file#add-a-package-output-to-a-feedstock (this is something new, I guess it was really added a few days ago).

[jslee02]

@traversaro Yeah, it seems like it's a new policy. I didn't encounter this when doing similar practice for momentum a few weeks ago.