-
Notifications
You must be signed in to change notification settings - Fork 423
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
Versions >=24.7.0
skip installing requirements for some multi-output recipes
#5444
Comments
I think you're running into a combination of two issues here. The first is that 24.7 started applying setting environment variables like However, it turns into a problem because you have named your outputs:
- name: solara
[...] is 100% ignored (c.f. #4172), and so it turns out that the "global" configuration section (which is mapped to The easiest solution is package:
- name: solara
+ name: solara-split
source: and extra:
+ feedstock-name: solara
recipe-maintainers:
- maartenbreddels Though of course it would be good for conda-build (or at least the conda-smithy linter) to warn on cases where the configuration of an output gets ignored. |
Because `PIP_` environmental variables are set in `conda-build` environments since version 7.24.0, and because our feedstock shared its name with one of the outputs, the `build` process of that output was effectively ignored. See conda/conda-build#5444 for details.
Thanks a lot @h-vetinari, that fixes our issue! I agree that it might be nice to get a warning from somewhere in this case. These name collisions resulting in issues could also be mentioned in the docs, for example at debugging conda recipes. Should this issue to stay open for future reference, like #4172? |
Because `PIP_` environmental variables are set in `conda-build` environments since version 7.24.0, and because our feedstock shared its name with one of the outputs, the `build` process of that output was effectively ignored. See conda/conda-build#5444 for details.
Checklist
What happened?
Upon an upgrade to
conda-build=24.7.1
, the build process for ourconda-forge
multi-output package solara broke. Looking at the build logs, I see that for the other "sub-packages" that are to be output (solara-ui
andsolara-server
), the output folder is reloaded, and a new environment is created (see attached excerpt from the logs) before the build script is executed. However, forsolara
this step is skipped, and the build script fails with aModuleNotFoundError
for hatchling.Log excerpt for `solara-server`
Log excerpt for `solara`
Limiting
conda-build<24.7.1
(which installs24.5.1
) fixes this issue.Conda Info
Conda Config
Conda list
No response
Additional Context
cc: @dhirschfeld, @mariobuikhuizen, @hmaarrfk
The text was updated successfully, but these errors were encountered: