Migrate recipe to rattler-build v1 format

[vicentebolea]

This PR updates the adios2-feedstock to use the new rattler-build v1
recipe format as introduced by CEP 13.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict.

Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found it was in an excellent condition.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory. You can also examine the workflow logs for more detail.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/19251666613. Examine the logs at this URL for more detail.}

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found it was in an excellent condition.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found some lint.

Here's what I've got...

For recipe/recipe.yaml:

• ❌ The top level meta key cache is unexpected

• ❌ In conda-forge.yml: $.linter = {'skip': ['unknown_meta_key', 'unknown_azure_setting', 'unknown_docker_setting']}.

  {'skip': ['unknown_meta_key', 'unknown_azure_setting', 'unknown_docker_setting']} is not valid under any of the given schemas

  Schema

  {
    "anyOf": [
      {
        "$ref": "#/$defs/LinterConfig"
      },
      {
        "type": "null"
      }
    ]
  }

• ❌ In conda-forge.yml: $.docker = {'run_args': '-e EXTRA_CB_OPTIONS'}.

  {'run_args': '-e EXTRA_CB_OPTIONS'} is not valid under any of the given schemas

  Schema

  {
    "anyOf": [
      {
        "$ref": "#/$defs/CondaForgeDocker"
      },
      {
        "type": "null"
      }
    ]
  }

• ❌ In conda-forge.yml: $.azure = {'settings_linux': {'variables': {'EXTRA_CB_OPTIONS': '--experimental'}}, 'settings_win': {'variables': {'RATTLER_BUILD_EXPERIMENTAL': True}}, 'settings_osx': {'variables': {'RATTLER_BUILD_EXPERIMENTAL': True}}}.

  {'settings_linux': {'variables': {'EXTRA_CB_OPTIONS': '--experimental'}}, 'settings_win': {'variables': {'RATTLER_BUILD_EXPERIMENTAL': True}}, 'settings_osx': {'variables': {'RATTLER_BUILD_EXPERIMENTAL': True}}} is not valid under any of the given schemas

  Schema

  {
    "anyOf": [
      {
        "$ref": "#/$defs/AzureConfig"
      },
      {
        "type": "null"
      }
    ]
  }

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/20319395865. Examine the logs at this URL for more detail.}

[ax3l]

@vicentebolea in case it helps, my MPI-varianted packages transitioned successfully to rattler here:

• Release 25.03, Transition to v1 format (recipe.yaml) amrex-feedstock#40
• pyamrex v25.03, Transition to v1 format (recipe.yaml) pyamrex-feedstock#32
• openpmd-api v0.16.1, Transition to v1 format (recipe.yaml) openpmd-api-feedstock#118
• warpx v25.03, Transition to v1 format (recipe.yaml) warpx-feedstock#101
• impactx v25.03, Transition to v1 format (recipe.yaml) impactx-feedstock#45

following the logic I found out here:

• https://prefix.dev/blog/rattler_build_on_conda_forge
• openpmd-api v0.16.1, Transition to v1 format (recipe.yaml) openpmd-api-feedstock#118
• recipe.yaml: fix build string openpmd-api-feedstock#119

[vicentebolea]

Thanks @ax3l for the references this is truly useful. Are any of these project using multiple outputs and the experimental cache feature?

[ax3l]

At least in my projects, I did not yet get to those features yet 😅

Do you have any refs? We can also check on Zulip with Wolf, sometimes he has a few cycles to help us rattle up :)

[vicentebolea]

Thanks @ax3l here is the feature that we needed from experimental: https://rattler-build.prefix.dev/dev/multiple_output_cache/

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict.

Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found it was in an excellent condition.

[vicentebolea]

waiting on: prefix-dev/rattler-build#2432

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found it was in an excellent condition.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory. You can also examine the workflow logs for more detail.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/24791027896. Examine the logs at this URL for more detail.}

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found it was in an excellent condition.

[conda-forge-admin]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed
• github-actions: passed

Thus the PR was passing and merged! Have a great day!