conda update -all may not be able to make everything the latest versions because you may have conflicting constraints in your environment. If any packages are orphaned by an update, they are removed. In doing so, it drops all the version constraints from the history and tries to make everything as new as it can.
This updates all packages in the current environment to the latest version. See all of the available Anaconda versions.Ĭonda update -all will unpin everything. As of conda 4.7, when a package loses its connection to the set of specs that have been requested in the past, it gets removed. conda install anaconda=VERSION-NUMBER may remove packages if the new metapackage that is replacing your old one has removed packages. The “custom” version is lower in version ordering than any actual release number. There is a special “custom” version of the Anaconda metapackage that has all the package dependencies, but none of them are constrained. That metapackage represents a pinned state that has undergone testing as a collection.
Conda 4.The below content provides more details about what is happening when you update Anaconda.Ĭonda install anaconda=VERSION-NUMBER grabs the specific release of the Anaconda metapackage for example, conda install anaconda=2022.05. If the user-specified version of a package does not meet the spec defined in the pinned file, Conda should fail. If you compare this list with the pinned file, you find that ca-certificates's version is also not what gets defined in the pinned file (pinned file has 2019.1.23). The following NEW packages will be INSTALLED:
The following packages will be downloaded: Solving environment: \ WARNING :_add_specs(583): pinned spec certifi=2019.3.9 conflicts with explicit specs. Overriding pinned spec.įailed with current_repodata.json, will retry with next repodata source.Ĭollecting package metadata (repodata.json): done Solving environment: | WARNING :_add_specs(583): pinned spec certifi=2019.3.9 conflicts with explicit specs.
0 kommentar(er)
