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 60581ea4cfe2d4536c5c2049c09e9f6998b4e9b0 #123

Open
conda-forge-daemon opened this issue Feb 9, 2021 · 5 comments

Comments

@conda-forge-daemon
Copy link

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

It appears that one or more of your feedstock's outputs is either invalid or
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, a feedstock output that is not allowed for that feedstock, or a feedstock output
with files that are not allowed for that output. 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.

error messages:

@conda-forge-webservices
Copy link
Contributor

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

error messages:

  • invalid feedstock token

@jakirkham
Copy link
Member

Was fixed in PR ( conda-forge/admin-requests#570 )

@conda-forge-webservices
Copy link
Contributor

Hi @conda-forge/conda-forge-repodata-patches! 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-repodata-patches-20230516.19.05.39-hd8ed1ab_0.conda: True

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

  • noarch/conda-forge-repodata-patches-20230516.19.05.39-hd8ed1ab_0.conda: False

@jakirkham
Copy link
Member

jakirkham commented May 17, 2023

Guessing this is either due the GH outage earlier or maybe issue ( conda-forge/conda-forge.github.io#1958 ). Restarting CI

We can revisit if there are still issues

Edit: Looks like it worked 🎉

@conda-forge-webservices
Copy link
Contributor

Hi @conda-forge/conda-forge-repodata-patches! 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 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

3 participants