Conda licence change - impact for xp65 users?

Hi folks,

At CSIRO we’ve just been notified that the changes to Anaconda licensing mean that as of Nov 1, we need to not have “defaults” in our channels list. It looks like xp65 analysis envs are built from “defaults” not “conda-forge”, do you know if xp65 is affected by this license change?

Thanks,
Claire

Hi Claire,

We are not using defaults as you can see if you do a conda list.

Most packages are from conda-forge, accessnri or pypi.

Romain

Huh. That’s interesting. Thanks @rbeucher .
Indeed, conda list looks (mostly) okay, but conda config --show channels gives a warning and shows defaults. When I build an env using xp65 as my base env and adding my own requirements.txt (following Building custom python environments on top of conda/analysis3 — CLEX CMS Blog) I find I end up with a bunch of packages from anaconda, which is odd.
I guess I probably need to set my user level config to use conda-forge, I wonder where that is inherited from.

Yes I noticed that. I’m trying to track that down. Not sure what is going on. It definitely does not use defaults anymore but the conda-lock files I have created still list defaults as an option. It shouldn’t… let’s see if we can fix that

Huh weird… thank you for looking into it! <3