Pierre-Olivier Simonard

What is the expected behavior ? Is the build supposed to fail, but catching the exception ? Or should the channel be added in the database ?

@peytondmurray I could make this work by adding `main` in the list of channels : ```yaml channels: - conda-forge - main dependencies: - hvplot - pip: - tqdm @ git+https://github.com/tqdm/tqdm@master...

Note regarding Conda Store API : My understanding here is that we will have to use two endpoints in a row : - First, trigger a build with the new...

After discussing with Chris during today's meeting, my previous comment is invalid : only the second step is needed. ➞ update the env this way (`PUT /api/v1/environment/// `)

The bug in #202 breaks the functionality for any namespace that is not default.

PR in progress : https://github.com/mamba-org/gator/pull/169

CLI now exists. This issue contains informations about desired features, hence marking it as META.

Alternatively to changing the API, we can achieve the same goal ( have the list of listed packages without the dependencies ) in a two-step way : Starting from a...

The API changed since the issue was open, and the performance were greatly improved since then. Do we still want this feature of listing versions of a given package ?

I've tried the given yaml. The env doesn’t build but there’s no more error from conda store, it’s “just” an R env that doesn’t build. I consider this fixed.