Jonas Haag
Jonas Haag
That’s really interesting. You used a recent compiler but the problem remains. I’m not sure what happens here. Are we getting an old libstdc++ even with the new compiler? (Because...
@isuruf my thinking is that when we fixed the compilation problems on @hannah413‘s machine we got the program to compile but it fails to find the temporary directory. My hypothesis...
Interactive, autocompleting, fuzzy search a la Google search would be nice.
`micromamba update -f myenv.yml` seems to ignore `myenv.yml`.
Yes that sounds reasonable as well. What would be the role of `micromamba update` in that case? Is it just a shorthand to `install --update`?
We just hit this again. Shall we remove the `--file` option from `update?
> But maybe it's better to let the micromamba self-modifications live outside the normal package management Strongly agree!
Going to try this in a funny customer environment :)
Tested on Windows with micromamba.exe in Downloads\: ``` error libmamba Could not lock non-existing path 'C:\Users\USERNAME\conda-meta' critical libmamba LockFile error. Aborting. ```
What did you expect do happen?