How to import base (root) environment to new device

Product Help
1

Hi. I have currently transferring data from my old laptop to a new pc and is trying to setup the same conda environments in the anaconda.

I backup all the conda environments on anaconda cloud, then import them back from the cloud. All the environments are successfully imported, besides of the base environment. I am trying to import the base environment as a new environment named “anaconda3”. But I got the error message:

PackagesNotFoundError: The following packages are not available from current channels:

- navigator-updater==0.5.0=py311haa95532_0

Current channels:

- https://conda.anaconda.org/conda-forge/win-64
- https://repo.anaconda.com/pkgs/main/win-64
- https://repo.anaconda.com/pkgs/r/win-64
- https://repo.anaconda.com/pkgs/msys2/win-64

To search for alternate channels that may provide the conda package you're
looking for, navigate to

https://anaconda.org

and use the search bar at the top of the page.

I have been using base environment as my main. How am I supposed to transfer it to my new pc?

2

Unfortunately, it looks like navigator-updater version 0.5.0 is no longer available in the repository (probably pulled for a good technical reason). I’d recommend installing v0.5.1. If you still have access to the old environment, you could upgrade that package, and then back it up again - and then you should be able to import it successfully. Or you could alter the yaml file directly itself if you have it locally.

As an aside, you are missing the noarch channels in your channels list.
i.e. main/noarch some packages are only available in noarch channels, so it is good to include those in your channel list.

4

Thanks for the reply. I do find how to install the navigator-updater v0.5.1.
But unfortunately, I accidentally deleted the entire anaconda distribution before successfully backup the base environment. So the current situation is that I have a base environment with navigator-updater v0.5.0 in anaconda cloud. Is there any way to save that?

for example, is it possible to generate the yaml file from the cloud backup?

5

Unfortunately, this is not implemented in a user friendly way yet.

You can try to track down the temporary file that Navigator creates when it attempts to import the environment. On Windows, that would most likely be in C:\\Users\<username>\AppData\Local\Temp - the last file with* .yml extension that has 32 hex digits in its name (assuming you are looking right after you attempt the import in Navigator)