Release 25.1.2.dev1 (continued from previous page) # Check whether fingerprint is correct (will output an error message otherwise) gpg --keyring /usr/share/keyrings/conda-archive-keyring.gpg --no-default-keyring essential to making the software in the environments work well. Activation entails two primary functions: adding entries to PATH for the environment and running any activation scripts that the environment PATH makes conda less disruptive to other software on your system. For more information, read the output from conda init --help. One setting may be useful to you when using conda init is: auto_activate_base:

Release 24.11.3.dev2 (continued from previous page) # Check whether fingerprint is correct (will output an error message otherwise) gpg --keyring /usr/share/keyrings/conda-archive-keyring.gpg --no-default-keyring essential to making the software in the environments work well. Activation entails two primary functions: adding entries to PATH for the environment and running any activation scripts that the environment PATH makes conda less disruptive to other software on your system. For more information, read the output from conda init --help. One setting may be useful to you when using conda init is: auto_activate_base:

conda.gpg /usr/share/keyrings/conda-archive-keyring.gpg # Check whether fingerprint is correct (will output an error message otherwise) gpg --keyring /usr/share/keyrings/conda-archive-keyring.gpg --no-default-keyring essential to making the software in the environments work well. Activation entails two primary functions: adding entries to PATH for the environment and running any activation scripts that the environment PATH makes conda less disruptive to other software on your system. For more information, read the output from conda init --help. One setting may be useful to you when using conda init is: auto_activate_base:

conda.gpg /usr/share/keyrings/conda-archive-keyring.gpg # Check whether fingerprint is correct (will output an error message otherwise) gpg --keyring /usr/share/keyrings/conda-archive-keyring.gpg --no-default-keyring essential to making the software in the environments work well. Activation entails two primary functions: adding entries to PATH for the environment and running any activation scripts that the environment PATH makes conda less disruptive to other software on your system. For more information, read the output from conda init --help. One setting may be useful to you when using conda init is: auto_activate_base:

has a name. It need not have any dependencies or build steps. Mutex metapackages are frequently an "output" in a recipe that builds some variant of another package. Mutex metapackages function as a tool to conda.gpg /usr/share/keyrings/conda-archive-keyring.gpg # Check whether fingerprint is correct (will output an error message otherwise) gpg --keyring /usr/share/keyrings/conda-archive-keyring.gpg --no-default-keyring packages with conda list. This does not affect any conda command or functionality other than the output of the command conda list. The default is True. EXAMPLE: use_pip: False 4.1. User guide 55 conda

conda.gpg /usr/share/keyrings/conda-archive-keyring.gpg # Check whether fingerprint is correct (will output an error message otherwise) gpg --keyring /usr/share/keyrings/conda-archive-keyring.gpg --no-default-keyring essential to making the software in the environments work well. Activation entails two primary functions: adding entries to PATH for the environment and running any activation scripts that the environment PATH makes conda less disruptive to other software on your system. For more information, read the output from conda init --help. One setting may be useful to you when using conda init is: auto_activate_base:

conda.gpg /usr/share/keyrings/conda-archive-keyring.gpg # Check whether fingerprint is correct (will output an error message otherwise) gpg --keyring /usr/share/keyrings/conda-archive-keyring.gpg --no-default-keyring essential to making the software in the environments work well. Activation entails two primary functions: adding entries to PATH for the environment and running any activation scripts that the environment PATH makes conda less disruptive to other software on your system. For more information, read the output from conda init --help. One setting may be useful to you when using conda init is: auto_activate_base:

conda.gpg /usr/share/keyrings/conda-archive-keyring.gpg # Check whether fingerprint is correct (will output an error message otherwise) gpg --keyring /usr/share/keyrings/conda-archive-keyring.gpg --no-default-keyring essential to making the software in the environments work well. Activation entails two primary functions: adding entries to PATH for the environment and running any activation scripts that the environment PATH makes conda less disruptive to other software on your system. For more information, read the output from conda init --help. One setting may be useful to you when using conda init is: auto_activate_base:

has a name. It need not have any dependencies or build steps. Mutex metapackages are frequently an "output" in a recipe that builds some variant of another package. Mutex metapackages function as a tool to conda.gpg /usr/share/keyrings/conda-archive-keyring.gpg # Check whether fingerprint is correct (will output an error message otherwise) gpg --keyring /usr/share/keyrings/conda-archive-keyring.gpg --no-default-keyring packages with conda list. This does not affect any conda command or functionality other than the output of the command conda list. The default is True. EXAMPLE: use_pip: False Configure conda for use

has a name. It need not have any dependencies or build steps. Mutex metapackages are frequently an "output" in a recipe that builds some variant of another package. Mutex metapackages function as a tool to conda.gpg /usr/share/keyrings/conda-archive-keyring.gpg # Check whether fingerprint is correct (will output an error message otherwise) gpg --keyring /usr/share/keyrings/conda-archive-keyring.gpg --no-default-keyring packages with conda list. This does not affect any conda command or functionality other than the output of the command conda list. The default is True. EXAMPLE: use_pip: False 4.1. User guide 55 conda