From 001701f49905b1ba837eb7b43eefb8150a06dec7 Mon Sep 17 00:00:00 2001 From: Cornelius Roemer Date: Thu, 11 Jul 2024 19:32:45 +0200 Subject: [PATCH] doc: mention that .mambarc channels are ignored (#25) As someone who uses mamba for everything, I didn't realize I had to manually add conda-forge and bioconda channels to `.condarc` The fact that there's no debug logging for conda possible through bioconda-utils made debugging harder, so this note could help others in the future who similarly use .mambarc but not .condarc Related to https://github.com/bioconda/bioconda-utils/issues/1006 --- source/contributor/building-locally.rst | 3 +++ 1 file changed, 3 insertions(+) diff --git a/source/contributor/building-locally.rst b/source/contributor/building-locally.rst index e674dd8..0368c9d 100644 --- a/source/contributor/building-locally.rst +++ b/source/contributor/building-locally.rst @@ -51,6 +51,9 @@ The above commands do the following: the recipes test in a clean, freshly created docker container to ensure that the package does not depend on anything that happens to be included in the build container. + - Make sure you have `bioconda` and `conda-forge` channels explicitly + added to your environment or your `.condarc`. It is not sufficient + to have those channels specified in `.mambarc`. If you do not have access to Docker, you can still run the basic test by omitting the ``--docker`` and ``--mulled-test`` options.