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

CLI: lint: Feedstock has no recipe/meta.yaml for v1 recipe #2225

Open
1 task done
lucascolley opened this issue Jan 21, 2025 · 1 comment
Open
1 task done

CLI: lint: Feedstock has no recipe/meta.yaml for v1 recipe #2225

lucascolley opened this issue Jan 21, 2025 · 1 comment
Labels

Comments

@lucascolley
Copy link
Member

Solution to issue cannot be found in the documentation.

  • I checked the documentation.

Issue

The linter passes in CI on conda-forge/scipy-stubs-feedstock#10, but locally I see

scipy-stubs-feedstock on πŸŽ‹ rattler [$] via 🐍 
❯ pixi run conda smithy lint
Traceback (most recent call last):
  File "/Users/lucascolley/programming/feedstocks/.pixi/envs/default/bin/conda-smithy", line 10, in <module>
    sys.exit(main())
             ^^^^^^
  File "/Users/lucascolley/programming/feedstocks/.pixi/envs/default/lib/python3.12/site-packages/conda_smithy/cli.py", line 767, in main
    args.subcommand_func(args)
  File "/Users/lucascolley/programming/feedstocks/.pixi/envs/default/lib/python3.12/site-packages/conda_smithy/cli.py", line 645, in __call__
    lints, hints = linter.main(
                   ^^^^^^^^^^^^
  File "/Users/lucascolley/programming/feedstocks/.pixi/envs/default/lib/python3.12/site-packages/conda_smithy/lint_recipe.py", line 734, in main
    raise OSError(
OSError: Feedstock has no recipe/meta.yaml

Installed packages

scipy-stubs-feedstock on πŸŽ‹ rattler [$] via 🐍 
❯ pixi ls | rg smithy
conda-smithy                3.45.3               unix_pyhd81877a_0   174.1 KiB  conda  conda-smithy

Environment info

n/a
@lucascolley
Copy link
Member Author

lucascolley commented Jan 22, 2025

the error here is resolved by passing recipe_directory or running the command from the directory of the recipe.

So the correct fix here is to improve the error message - it can happen if there is no recipe/meta.yaml, but also if there is no recipe.yaml in the cwd when the command is run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant