-
Notifications
You must be signed in to change notification settings - Fork 475
Open
Labels
type::featurerequest for a new feature or capabilityrequest for a new feature or capability
Description
Checklist
- I added a descriptive title
- I searched open requests and couldn't find a duplicate
What is the idea?
If you want to see a verbose output of the resolution (Etc. etc.), conda-build provides
$ conda debug --debug recipe
DEBUG conda.gateways.logging:set_log_level(223): log_level set to 10
usage: conda debug [-h] [-V] [-n] [--python PYTHON] [--perl PERL] [--numpy NUMPY] [--R R_BASE] [--lua LUA] [--append-file APPEND_SECTIONS_FILE] [--clobber-file CLOBBER_SECTIONS_FILE] [-m VARIANT_CONFIG_FILES] [-e EXCLUSIVE_CONFIG_FILES] [--use-channeldata] [--variants VARIANTS] [-c CHANNEL] [--use-local] [--override-channels]
[--repodata-fn REPODATA_FNS] [--experimental {jlap,lock}] [--no-lock] [--repodata-use-zst | --no-repodata-use-zst] [-p PATH] [-o OUTPUT_ID] [-a]
recipe_or_package_file_path
conda debug: error: unrecognized arguments: --debug
as an option. However, if you want the same information for conda debug this does not work (tested on conda-debug 25.7.0)
Why is this needed?
I periodically see differences in how conda build and conda debug resolve environments. The debug flag allows for more verbose output during build, but it missing during debug means that I cannot compare.
What should happen?
The --debug flag should turn on verbose/debugging information, same as for conda build.
Additional Context
No response
Metadata
Metadata
Assignees
Labels
type::featurerequest for a new feature or capabilityrequest for a new feature or capability