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
With the miniconda installer built with constructor 2, I was able to run bash miniconda-installer.sh -b -f -p ~/pre-existing-prefix to essentially recreate a base conda environment / installation, regardless of what other conda environments may exist (and importantly, leaving those intact). As of constructor 3, I find that this process doesn't work. It instead looks like the installation process is considering a lot of pre-existing packages and then attempting to install them alongside the bundled packages. It is invoking the solver and failing with conflicts (I thought constructor was supposed to just straight install bundled packages?). Pointing it to a new prefix (~/miniconda-empty) worked as expected.
(Not shown: during "extracting packages" rather than the few packages I'd expected bundled with miniconda, I saw it working through 300+ packages).
Is the force mechanism still supported? Do we always need to install to a new/clean location or should we be able to install on top of a prior location?
❯ wget https://repo.anaconda.com/miniconda/Miniconda3-py39_4.10.3-MacOSX-x86_64.sh
❯ bash Miniconda3-py39_4.10.3-MacOSX-x86_64.sh -f -b -p ~/miniconda
PREFIX=/Users/hajapy/miniconda
Unpacking payload ...
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: /
Found conflicts! Looking for incompatible packages.
This can take several minutes. Press CTRL-C to abort.
failed
UnsatisfiableError: The following specifications were found to be incompatible with each other:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.
If you would like this issue to remain open please:
Verify that you can still reproduce the issue at hand
Comment that the issue is still reproducible and include:
- What OS and version you reproduced the issue on
- What steps you followed to reproduce the issue
NOTE: If this issue was closed prematurely, please leave a comment.
With the miniconda installer built with constructor 2, I was able to run
bash miniconda-installer.sh -b -f -p ~/pre-existing-prefix
to essentially recreate a base conda environment / installation, regardless of what other conda environments may exist (and importantly, leaving those intact). As of constructor 3, I find that this process doesn't work. It instead looks like the installation process is considering a lot of pre-existing packages and then attempting to install them alongside the bundled packages. It is invoking the solver and failing with conflicts (I thought constructor was supposed to just straight install bundled packages?). Pointing it to a new prefix (~/miniconda-empty) worked as expected.(Not shown: during "extracting packages" rather than the few packages I'd expected bundled with miniconda, I saw it working through 300+ packages).
Is the force mechanism still supported? Do we always need to install to a new/clean location or should we be able to install on top of a prior location?
Conflict details
The text was updated successfully, but these errors were encountered: