Question
PackageNotFoundError during environment resolution in Anaconda
Zo Indigo
0 reputation · 13 Feb 2022, 10:00 UTC
126.3K views1
Loading…
0 reputation · 13 Feb 2022, 10:00 UTC
Anaconda utilizes a local package cache directory to store downloaded packages and index metadata, reducing redundant network requests during environment creation. However, a discrepancy can arise when the local index cache refers to a package version that is no longer available on the remote channel repository.
When the solver prioritizes this stale cached metadata over the current remote state, it may attempt to resolve dependencies using a version that cannot be retrieved, leading to a failure in the environment solve process.
Given the different metadata refresh behaviors between the classic Conda solver and the libmamba solver, what are the specific triggers that cause the solver to rely on stale cache results instead of fetching the latest remote index? Does the conda clean -i command permanently resolve this state, or is a temporary flag required during the install command to bypass the local index?
To resolve a PackageNotFoundError caused by stale metadata, the most effective method is to clear the index cache and force a fresh synchronization with the remote repositories.
The conda clean -i command permanently removes the local index cache. This forces the solver to fetch the latest repodata.json from all configured channels during the next operation, effectively eliminating the discrepancy between the local cache and the remote state.
anacondaconda clean -iconda install <package_name>If the error persists, you can bypass the cache for a single command using the --no-cache flag (available in newer versions/solvers) or by ensuring your channels are up to date via conda update --all.
The trigger for relying on stale cache results is typically the cache expiration logic. Conda stores metadata locally to avoid downloading large JSON files on every command. If the remote repository removes a package version or modifies a build string, but the local cache has not yet reached its expiration threshold, the solver will attempt to request a file that no longer exists on the server.
PackageNotFoundError or a 404 error during the download phase because it trusted the local index during the resolution phase.To verify if the package is actually available to the solver after cleaning the cache, run:
conda search <package_name>Missing Diagnostic Detail: To provide a more tailored recommendation, please specify if you are using strict channel priority (channel_priority: strict). If strict priority is enabled, the solver may ignore a valid package in a lower-priority channel even if the cache is fresh.
Use comments to ask for clarification. Post a solution as an answer.
32,775 reputation · 13 Feb 2022, 16:39 UTC
While clearing the index cache resolves metadata discrepancies, it is useful to verify if a package is actually available for your specific platform architecture before re-running a full environment solve. A PackageNotFoundError can sometimes be misattributed to stale cache when the package simply doesn't exist for the current OS or architecture (e.g., attempting to install a linux-64 build on osx-arm64).
To isolate whether the issue is a cache error or a compatibility gap, you can use the search command:
conda search <package_name>If the search returns no results despite the package existing on the remote channel, it confirms a metadata or architecture mismatch. You can further verify your active platform settings by running conda info to ensure the solver is targeting the correct subdirectory of the remote repository.