-
Notifications
You must be signed in to change notification settings - Fork 24
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
Conda build 3.28.1 fails with libmamba solver 23.12.0 with KeyError
#409
Comments
I have questions about the config.
Sorry for the brevity, typing from my phone 😅 |
Thanks for your comments! The config is coming straight from Artifactory documentation itself. Additionally, we have been using this config for more than 2 years now for both installing and building packages and it has worked just fine until now with the new solver. If you still think it's an issue with the config, I am happy to test whatever changes you might suggest. |
Yes, we should revisit that configuration. Maybe it worked for classic, but there are certain inconsistencies that we have been trying to address with libmamba. Let me elaborate on why I think some aspects of your configuration are redundant:
Let's recap with examples:
Note, you can ALSO fetch packages from conda-forge by setting Now, back to your configuration. I'm not sure how Artifactory works, but I assume To use # channel_alias; remove
channels:
- https://artifactory.ets.org/artifactory/api/conda/conda-virtual
# default_channels; remove Same, but # channel_alias; remove
# channels; remove
default_channels:
- https://artifactory.ets.org/artifactory/api/conda/conda-virtual To only use Artifactory as a source and allow channel_alias: https://artifactory.ets.org/artifactory/api/conda
channels:
- conda-virtual
# default_channels; remove to restore `-c defaults` meaning Anaconda's `pkgs/main` Same but channel_alias: https://artifactory.ets.org/artifactory/api/conda
channels:
- conda-virtual
default_channels:
- https://artifactory.ets.org/artifactory/api/conda/conda-virtual There are more ways to configure things, but the main issue I see is having Hope that's clear to an extent 😬 |
Btw, https://conda.io/projects/conda/en/latest/configuration.html lists and describes all the config options available. Search for |
Thank you for the detailed explanation 🙏! I'll try out some of the things you suggested and report back. |
Okay, I finally had a chance to try out your suggestion. I changed my channel_alias: https://artifactory.ets.org/artifactory/api/conda
channels:
- conda-virtual
default_channels:
- https://artifactory.ets.org/artifactory/api/conda/conda-virtual However, if I try to build the package now, I get a 500 error like so:
We are using |
I see, yes, your assessment is correct. You can either delete the custom_channels:
conda-forge: https://conda.anaconda.org |
That works perfectly! Thank you so much all your help! |
Checklist
What happened?
We use a local Artifactory instance to host our internal packages and a conda-forge cache. Just like with #363, a KeyError is generated when building a conda package as shown below:
Traceback
I can build the package successfully if I set the
CONDA_SOLVER
environment variable toclassic
when building the package.Conda Info
Conda Config
Conda list
Additional Context
No response
The text was updated successfully, but these errors were encountered: