Cannot install additional dependencies when using micromamba lock installation
pavelzw opened this issue · comments
When creating an environment with micromamba and specifying a lock file with additional packages to install, micromamba only takes care of the lock file but not the additional packages.
Example:
lockfile.lock
@EXPLICIT
https://conda.anaconda.org/conda-forge/linux-64/numpy-1.21.6-py37h976b520_0.tar.bz2#b0701d8dc4849b6e06caf1c84135c13c
❯ micromamba create -n testenv -y -f lockfile.lock pytest
__
__ ______ ___ ____ _____ ___ / /_ ____ _
/ / / / __ `__ \/ __ `/ __ `__ \/ __ \/ __ `/
/ /_/ / / / / / / /_/ / / / / / / /_/ / /_/ /
/ .___/_/ /_/ /_/\__,_/_/ /_/ /_/_.___/\__,_/
/_/
Transaction
Prefix: /Users/pavelzwerschke/micromamba/envs/testenv
Updating specs:
- conda-forge/linux-64::numpy==1.21.6=py37h976b520_0[md5=b0701d8dc4849b6e06caf1c84135c13c]
Package Version Build Channel Size
────────────────────────────────────────────────────────────
Install:
────────────────────────────────────────────────────────────
+ numpy 1.21.6 py37h976b520_0 conda-forge Cached
Summary:
Install: 1 packages
Total download: 0 B
────────────────────────────────────────────────────────────
Transaction starting
Linking numpy-1.21.6-py37h976b520_0
Transaction finished
@pavelzw I've looked into the code for this and it seems doable to implement this feature.
However I wonder if it's at all sound because the order of installing dependencies matters (must be topological; this is given in the @EXPLICIT file). Adding a new dependency to explicit file specs generally requires that the combined set of dependencies be re-ordered (hence, re-solved).
let's not move forward with this, lockfiles are locked for a reason 😄