(collections of PackageRecord objects): • Installed pool: The installed packages, grouped by name. Each group should only contain one record! • Explicit pool: The full index, but reduced for the specs in requested Processing specs for conda install Preparation 1. Generate the explicit pool for the requested specs (via Resolve._get_package_pool()). 2. Detect potential conflicts (via (Resolve.get_conflicting_specs()) 10.1.dev3 • The package name cannot be found in the explicit pool index or, if it is, the installed match can be found in that explicit pool (to guarantee it will be found instead of creating one more conflict

(collections of PackageRecord objects): • Installed pool: The installed packages, grouped by name. Each group should only contain one record! • Explicit pool: The full index, but reduced for the specs in requested Processing specs for conda install Preparation 1. Generate the explicit pool for the requested specs (via Resolve._get_package_pool()). 2. Detect potential conflicts (via (Resolve.get_conflicting_specs()) 11.1.dev1 • The package name cannot be found in the explicit pool index or, if it is, the installed match can be found in that explicit pool (to guarantee it will be found instead of creating one more conflict

(collections of PackageRecord objects): • Installed pool: The installed packages, grouped by name. Each group should only contain one record! • Explicit pool: The full index, but reduced for the specs in requested Processing specs for conda install Preparation 1. Generate the explicit pool for the requested specs (via Resolve._get_package_pool()). 2. Detect potential conflicts (via (Resolve.get_conflicting_specs()) conflict, and • The package name cannot be found in the explicit pool index or, if it is, the installed match can be found in that explicit pool (to guarantee it will be found instead of creating one more conflict

(collections of PackageRecord objects): • Installed pool: The installed packages, grouped by name. Each group should only contain one record! • Explicit pool: The full index, but reduced for the specs in requested Processing specs for conda install Preparation 1. Generate the explicit pool for the requested specs (via Resolve._get_package_pool()). 2. Detect potential conflicts (via (Resolve.get_conflicting_specs()) conflict, and • The package name cannot be found in the explicit pool index or, if it is, the installed match can be found in that explicit pool (to guarantee it will be found instead of creating one more conflict

(collections of PackageRecord objects): • Installed pool: The installed packages, grouped by name. Each group should only contain one record! • Explicit pool: The full index, but reduced for the specs in requested Processing specs for conda install Preparation 1. Generate the explicit pool for the requested specs (via Resolve._get_package_pool()). 2. Detect potential conflicts (via (Resolve.get_conflicting_specs()) conflict, and • The package name cannot be found in the explicit pool index or, if it is, the installed match can be found in that explicit pool (to guarantee it will be found instead of creating one more conflict

(collections of PackageRecord objects): • Installed pool: The installed packages, grouped by name. Each group should only contain one record! • Explicit pool: The full index, but reduced for the specs in requested Processing specs for conda install Preparation 1. Generate the explicit pool for the requested specs (via Resolve._get_package_pool()). 2. Detect potential conflicts (via (Resolve.get_conflicting_specs()) conflict, and • The package name cannot be found in the explicit pool index or, if it is, the installed match can be found in that explicit pool (to guarantee it will be found instead of creating one more conflict

welcome conda, Release 25.1.2.dev1 • Installed pool: The installed packages, grouped by name. Each group should only contain one record! • Explicit pool: The full index, but reduced for the specs in requested Processing specs for conda install Preparation 1. Generate the explicit pool for the requested specs (via Resolve._get_package_pool()). 2. Detect potential conflicts (via (Resolve.get_conflicting_specs()) conflict, and • The package name cannot be found in the explicit pool index or, if it is, the installed match can be found in that explicit pool (to guarantee it will be found instead of creating one more conflict

(collections of PackageRecord objects): • Installed pool: The installed packages, grouped by name. Each group should only contain one record! • Explicit pool: The full index, but reduced for the specs in requested Processing specs for conda install Preparation 1. Generate the explicit pool for the requested specs (via Resolve._get_package_pool()). 2. Detect potential conflicts (via (Resolve.get_conflicting_specs()) conflict, and • The package name cannot be found in the explicit pool index or, if it is, the installed match can be found in that explicit pool (to guarantee it will be found instead of creating one more conflict

welcome conda, Release 24.9.3.dev1 • Installed pool: The installed packages, grouped by name. Each group should only contain one record! • Explicit pool: The full index, but reduced for the specs in requested Processing specs for conda install Preparation 1. Generate the explicit pool for the requested specs (via Resolve._get_package_pool()). 2. Detect potential conflicts (via (Resolve.get_conflicting_specs()) conflict, and • The package name cannot be found in the explicit pool index or, if it is, the installed match can be found in that explicit pool (to guarantee it will be found instead of creating one more conflict

Contributors welcome conda, Release 24.7.1 • Installed pool: The installed packages, grouped by name. Each group should only contain one record! • Explicit pool: The full index, but reduced for the specs in requested Processing specs for conda install Preparation 1. Generate the explicit pool for the requested specs (via Resolve._get_package_pool()). 2. Detect potential conflicts (via (Resolve.get_conflicting_specs()) conflict, and • The package name cannot be found in the explicit pool index or, if it is, the installed match can be found in that explicit pool (to guarantee it will be found instead of creating one more conflict