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

[conda-forge-webservices]

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

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

• linux-64/ipopt-3.14.16-hfa21eaf_8.conda: False

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

• linux-64/ipopt-3.14.16-hfa21eaf_8.conda: False

error messages:

• output linux-64/ipopt-3.14.16-hfa21eaf_8.conda does not have a valid md5 checksum

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]

This is trange, the error complains about linux-64, but that can be installed without problems. The package that has problems is osx-64:

traversaro@IITBMP014LW012:~$ CONDA_SUBDIR=osx-64 conda create -n testipoptosx ipopt=3.14.16=*_8
Channels:
 - robostack-staging
 - conda-forge
Platform: osx-64
Collecting package metadata (repodata.json): done
Solving environment: failed

PackagesNotFoundError: The following packages are not available from current channels:

  - ipopt==3.14.16[build=*_8]

Current channels:

  - https://conda.anaconda.org/robostack-staging
  - https://conda.anaconda.org/conda-forge

To search for alternate channels that may provide the conda package you're
looking for, navigate to

    https://anaconda.org

and use the search bar at the top of the page.

indeed, going in https://anaconda.org/conda-forge/ipopt/files and clicking on osx-64 *_8 package results in this error:

<Error>
<Code>NoSuchKey</Code>
<Message>The specified key does not exist.</Message>
<Key>5f86b625a58f0d0a54298a0f/66f5a4598bbc84b7f4e6b4c4</Key>
<RequestId>84CFPRYWW33HEYFN</RequestId>
<HostId>
dAP4rsUXvBXJ4cxB0MVLRJNizexbRXR9/vsoo18bvQ9/bfWRlXcQaiB/yjVelvL7gTD9koSsZtrr1lBA5OZuayXvGpLb80IgLM5GK5p0gY0=
</HostId>
</Error>

Anyhow, I did a empty commit in #118 as the issue template suggested.

[traversaro]

This is possibly related: conda/infrastructure#1031 .

[traversaro]

As we now have fully working _9 builds, I think we can close this.