-
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
conda-build broken on Ubuntu20/22 #4993
Comments
That appears to be a deprecation warning. Is that command actually broken? Does using the recommended invocation of that command fix your issue? (i.e. We will be removing the ability to |
Also, if the warning output is giving you a problem, you could just the redirect that output elsewhere:
Hope that helps, but still, please find a way to stop using that particular invocation of that command 😄. |
Actually.... 😅 I see why this is weird now:
Even using the suggested invocation is still producing that warning message 😤. |
I am also experiencing this error, both |
Hi there, thank you for your contribution! This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs. If you would like this issue to remain open please:
NOTE: If this issue was closed prematurely, please leave a comment. Thanks! |
Checklist
What happened?
After installing conda-build on Ubuntu20 or 22 through anaconda, miniconda, or mamba, we are seeing the following error upon issuance of
conda-build
orconda index
commands.(3.9.0.sep5v2) vapor@vapor-Precision-Tower-5810:~$ conda-build --version /home/vapor/mambaforge/envs/3.9.0.sep5v2/bin/conda-build:11: DeprecationWarning: conda_build.cli.main_build.main is deprecated and will be removed in 4.0.0. Use
conda buildinstead. sys.exit(main()) conda-build 3.26.1
This seems to be platform specific as my team is not experiencing this on OSX.
This is seen in conda-build 3.26.1. Degrading to conda-build 3.24.0 resolves this issue.
Conda Info
Conda Config
Conda list
Additional Context
No response
The text was updated successfully, but these errors were encountered: