You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- If you export an environment using a lockfile and reproduce you might get an incompatible sysroot.
50
+
- MRB: Is there a shim we can use to use the system bits with our compilers? Is this PR providing that solution or a different one?
51
+
- IF: It's a slightly different problem. With this PR, users will get the most recent sysroot available for their system (instead of the pinned/oldest one). Currently, 2.28 in conda-forge.
52
+
- MRB: Are both solutions compatible?
53
+
- IF: They are compatible. Using the system sysroot should be explicitly opt-in (only if "they know what they are doing"). We shouldn't encourage it and instead prefer the "latest compatible one" provided by conda-forge.
54
+
- IF: The lockfile incompatibility problem is trying to install it in an older GLIBC system. The lockfile should include the `__glibc` virtual package in these cases.
55
+
- JRG: Capture this in an issue in conda/conda and maybe a CEP.
56
+
-[x] (JRG) Improvements in CI provisioning times in Windows / macOS:
57
+
- Windows-only: move base install to D:
58
+
- Both: use micromamba by default
59
+
- Linux: still using Docker images... how to approach this? new series of Docker images with suffixed names so they don't use `Miniforge` installs? We can keep the same pinning entries, but not sure how hacky this feels.
60
+
- IF: Add micromamba to the Docker images. The added size is negligible, and just use micromamba instead of Miniforge to provision the base environment. Make sure to use the same cache.
0 commit comments