it seems that this is just a problem with the generation script.
Please see the repo readme for directions on how to make PRs on this repo.
Checklist:
[ ] if you have added a CDT, it appears in the cdt_slugs.yaml file and
you have rerun the script python gen_cdt_recipes.py.
[ ] if you have changed the CDT generator code (rpm.py), you have bumped
the build number in conda_build_config.yaml and have remade all of the
recipes via running python gen_cdt_recipes.py --force
[ ] if you have added a custom CDT recipe, you have added the name of the CDT
with custom: true in the cdt_slugs.yaml file.
[ ] all CDT recipes have build number set by {{ cdt_build_number }} for
old-style/legacy CDTs or {{ cdt_build_number|int + 1000 }} for new-style CDTs
[ ] if you see a warning about a CDT not having a license, you have added the
license_file key in the cdt_slugs.yaml file with the path to the appropriate
license in licenses/
NOTE: If you make any changes to cd_slugs.yaml, you need to reun the generator code
via python gen_cdt_recipes.py.
Do I really need to bump the cdt number in https://github.com/conda-forge/cdt-builds#changing-the-cdt-generation-script-rpmpy
it seems that this is just a problem with the generation script.
Please see the repo readme for directions on how to make PRs on this repo.
Checklist:
cdt_slugs.yamlfile and you have rerun the scriptpython gen_cdt_recipes.py.rpm.py), you have bumped the build number inconda_build_config.yamland have remade all of the recipes via runningpython gen_cdt_recipes.py --forcecustom: truein thecdt_slugs.yamlfile.{{ cdt_build_number }}for old-style/legacy CDTs or{{ cdt_build_number|int + 1000 }}for new-style CDTslicense_filekey in thecdt_slugs.yamlfile with the path to the appropriate license inlicenses/NOTE: If you make any changes to
cd_slugs.yaml, you need to reun the generator code viapython gen_cdt_recipes.py.