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 448cd71055c1672eaa58b800c57d609fe2b8b473 #55

Open
conda-forge-webservices bot opened this issue Dec 6, 2024 · 4 comments

Comments

@conda-forge-webservices
Copy link
Contributor

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

error messages:

  • invalid feedstock token
@Tobias-Fischer
Copy link
Contributor

I pushed dcf5152

@Tobias-Fischer
Copy link
Contributor

Despite the token reset the upload still doesn’t work - I’m not sure what’s going on @traversaro

@conda-forge-webservices
Copy link
Contributor Author

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

error messages:

  • invalid feedstock token

@traversaro
Copy link
Contributor

Let's try to do a new build.

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

2 participants