Install "compatible" package in package manager failing

CordulaGöke — Wed, 14 Jan 2026 13:05:13 GMT

I would like to install pyogrio to my cloned environment (ArcGIS Pro 3.6, installed on Monday). It is failing. I have cloned and installed only via the manager, not from outside ArcGIS. Could it be connected to an earlier package installation or is this a bug? Or does "compatible" not mean it is installable in the environment, it might only trying to find a compatible package?

None of the available versions seems to be compatible with the Pins in the environment

LibMambaUnsatisfiableError: Encountered problems while solving:
- nothing provides _python_rc needed by python-3.14.0rc2-h6fd79ff_100_cp314
Could not solve for environment specs
The following packages are incompatible
├─ arcpy-base is installable with the potential options
│ ├─ arcpy-base 3.6 would require
│ │ └─ libxml2 >=2.14.5,<2.15 with the potential options
│ │ ├─ libxml2 2.14.5, which can be installed;
│ │ └─ libxml2 [2.14.5|2.14.6] would require
│ │ └─ liblzma >=5.8.1,<6.0a0 with the potential options
│ │ ├─ liblzma 5.8.1 would require
│ │ │ └─ xz ==5.8.1 *_0, which can be installed;
│ │ └─ liblzma 5.8.1 would require
│ │ └─ xz 5.8.1.* , which can be installed;
│ └─ arcpy-base [3.1|3.2|3.3|3.4|3.5], which can be installed;
├─ pin-13 is not installable because it requires
│ └─ arcpy-base 3.6** , which conflicts with any installable versions previously reported;
├─ pin-2 is installable and it requires
│ └─ python 3.13** , which can be installed;
├─ pyogrio is installable with the potential options
│ ├─ pyogrio [0.10.0|0.9.0] would require
│ │ └─ libgdal-core >=3.9.2,<3.10.0a0 with the potential options
│ │ ├─ libgdal-core [3.9.2|3.9.3] would require
│ │ │ └─ libxml2 >=2.12.7,<2.14.0a0 , which conflicts with any installable versions previously reported;
│ │ ├─ libgdal-core [3.10.3|3.11.0|...|3.9.3] would require
│ │ │ └─ liblzma >=5.8.1,<6.0a0 , which can be installed (as previously explained);
│ │ ├─ libgdal-core [3.10.0|3.10.1|3.9.3] would require
│ │ │ └─ liblzma >=5.6.3,<6.0a0 with the potential options
│ │ │ ├─ liblzma 5.6.3 would require
│ │ │ │ └─ xz ==5.6.3 *_0, which can be installed;
│ │ │ ├─ liblzma 5.6.3 would require
│ │ │ │ └─ xz ==5.6.3 *_1, which can be installed;
│ │ │ ├─ liblzma 5.6.4 would require
│ │ │ │ └─ xz ==5.6.4 *_0, which can be installed;
│ │ │ ├─ liblzma 5.8.1, which can be installed (as previously explained);
│ │ │ └─ liblzma 5.8.1, which can be installed (as previously explained);
│ │ ├─ libgdal-core [3.10.0|3.9.3] would require
│ │ │ └─ libxml2 >=2.13.4,<2.14.0a0 , which conflicts with any installable versions previously reported;
│ │ ├─ libgdal-core [3.10.0|3.9.3] would require
│ │ │ └─ libxml2 >=2.13.5,<2.14.0a0 , which conflicts with any installable versions previously reported;
│ │ └─ libgdal-core [3.10.2|3.9.3] would require
│ │ └─ liblzma >=5.6.4,<6.0a0 , which can be installed (as previously explained);
│ ├─ pyogrio [0.10.0|0.11.0|...|0.9.0] would require
│ │ └─ python >=3.10,<3.11.0a0 , which conflicts with any installable versions previously reported;
│ ├─ pyogrio [0.10.0|0.11.0|...|0.9.0] would require
│ │ └─ python >=3.11,<3.12.0a0 , which conflicts with any installable versions previously reported;
│ ├─ pyogrio [0.10.0|0.11.0|...|0.9.0] would require
│ │ └─ python >=3.12,<3.13.0a0 , which conflicts with any installable versions previously reported;
│ ├─ pyogrio [0.10.0|0.11.0|0.11.1] would require
│ │ └─ libgdal-core [>=3.11.0,<3.12.0a0 |>=3.11.3,<3.12.0a0 ] with the potential options
│ │ ├─ libgdal-core [3.10.3|3.11.0|...|3.9.3], which can be installed (as previously explained);
│ │ └─ libgdal-core [3.11.0|3.11.4] would require
│ │ └─ xz >=5.6.4,<6.0a0 , which can be installed;
│ ├─ pyogrio 0.10.0 would require
│ │ └─ libgdal >=3.6.2,<3.7.0a0 with the potential options
│ │ ├─ libgdal 3.6.2 would require
│ │ │ └─ libxml2 >=2.10.3,<2.11.0a0 with the potential options
│ │ │ ├─ libxml2 2.10.3 conflicts with any installable versions previously reported;
│ │ │ ├─ libxml2 2.10.4 conflicts with any installable versions previously reported;
│ │ │ └─ libxml2 [2.10.3|2.10.4] would require
│ │ │ └─ zlib >=1.2.13,<1.3.0a0 , which can be installed;
│ │ ├─ libgdal 3.6.2 would require
│ │ │ └─ libxml2 >=2.13.1,<2.14.0a0 , which conflicts with any installable versions previously reported;
│ │ ├─ libgdal 3.6.2 would require
│ │ │ └─ libxml2 >=2.9.14,<2.10.0a0 with the potential options
│ │ │ ├─ libxml2 2.9.14 conflicts with any installable versions previously reported;
│ │ │ ├─ libxml2 2.9.14 would require
│ │ │ │ └─ zlib >=1.2.11,<1.3.0a0 , which can be installed;
│ │ │ └─ libxml2 2.9.14 would require
│ │ │ └─ zlib >=1.2.12,<1.3.0a0 , which can be installed;
│ │ ├─ libgdal 3.6.2 would require
│ │ │ └─ libxml2 >=2.10.4,<2.11.0a0 with the potential options
│ │ │ ├─ libxml2 2.10.4 conflicts with any installable versions previously reported;
│ │ │ └─ libxml2 [2.10.3|2.10.4], which can be installed (as previously explained);
│ │ ├─ libgdal 3.6.2 would require
│ │ │ └─ xz >=5.6.4,<6.0a0 , which can be installed;
│ │ ├─ libgdal 3.6.2 would require
│ │ │ └─ libxml2 >=2.13.5,<2.14.0a0 , which conflicts with any installable versions previously reported;
│ │ ├─ libgdal [3.6.2|3.6.3] would require
│ │ │ └─ libxml2 >=2.10.3,<2.14.0a0 with the potential options
│ │ │ ├─ libxml2 [2.13.1|2.13.3] conflicts with any installable versions previously reported;
│ │ │ ├─ libxml2 [2.13.5|2.13.6|2.13.7|2.13.8|2.13.9] conflicts with any installable versions previously reported;
│ │ │ ├─ libxml2 [2.12.10|2.12.7|2.12.9] conflicts with any installable versions previously reported;
│ │ │ ├─ libxml2 2.13.4 conflicts with any installable versions previously reported;
│ │ │ ├─ libxml2 2.10.3 conflicts with any installable versions previously reported;
│ │ │ ├─ libxml2 2.10.4 conflicts with any installable versions previously reported;
│ │ │ ├─ libxml2 [2.10.3|2.10.4], which can be installed (as previously explained);
│ │ │ ├─ libxml2 2.11.3 conflicts with any installable versions previously reported;
│ │ │ ├─ libxml2 2.11.4 conflicts with any installable versions previously reported;
│ │ │ └─ libxml2 [2.11.5|2.11.6|...|2.12.6] conflicts with any installable versions previously reported;
│ │ ├─ libgdal [3.6.3|3.6.4] would require
│ │ │ └─ libxml2 >=2.10.4,<2.14.0a0 with the potential options
│ │ │ ├─ libxml2 [2.13.1|2.13.3] conflicts with any installable versions previously reported;
│ │ │ ├─ libxml2 [2.13.5|2.13.6|2.13.7|2.13.8|2.13.9] conflicts with any installable versions previously reported;
│ │ │ ├─ libxml2 [2.12.10|2.12.7|2.12.9] conflicts with any installable versions previously reported;
│ │ │ ├─ libxml2 2.13.4 conflicts with any installable versions previously reported;
│ │ │ ├─ libxml2 2.10.4 conflicts with any installable versions previously reported;
│ │ │ ├─ libxml2 [2.10.3|2.10.4], which can be installed (as previously explained);
│ │ │ ├─ libxml2 2.11.3 conflicts with any installable versions previously reported;
│ │ │ ├─ libxml2 2.11.4 conflicts with any installable versions previously reported;
│ │ │ └─ libxml2 [2.11.5|2.11.6|...|2.12.6] conflicts with any installable versions previously reported;
│ │ ├─ libgdal 3.6.4 would require
│ │ │ └─ libxml2 >=2.11.5,<2.14.0a0 , which conflicts with any installable versions previously reported;
│ │ ├─ libgdal 3.6.4 would require
│ │ │ └─ libxml2 >=2.11.4,<2.14.0a0 , which conflicts with any installable versions previously reported;
│ │ └─ libgdal 3.6.4 would require
│ │ └─ libxml2 >=2.11.3,<2.14.0a0 , which conflicts with any installable versions previously reported;
│ ├─ pyogrio [0.10.0|0.11.1|0.12.0|0.12.1] would require
│ │ └─ python >=3.14,<3.15.0a0 , which conflicts with any installable versions previously reported;
│ ├─ pyogrio [0.10.0|0.11.0|...|0.9.0] would require
│ │ └─ python >=3.9,<3.10.0a0 , which conflicts with any installable versions previously reported;
│ ├─ pyogrio [0.2.0|0.3.0|...|0.9.0] would require
│ │ └─ python >=3.8,<3.9.0a0 , which conflicts with any installable versions previously reported;
│ ├─ pyogrio 0.10.0 would require
│ │ └─ libgdal-core >=3.10.0,<3.11.0a0 with the potential options
│ │ ├─ libgdal-core [3.10.3|3.11.0|...|3.9.3], which can be installed (as previously explained);
│ │ ├─ libgdal-core [3.10.0|3.10.1|3.9.3], which can be installed (as previously explained);
│ │ ├─ libgdal-core [3.10.0|3.9.3], which cannot be installed (as previously explained);
│ │ ├─ libgdal-core [3.10.0|3.9.3], which cannot be installed (as previously explained);
│ │ └─ libgdal-core [3.10.2|3.9.3], which can be installed (as previously explained);
│ ├─ pyogrio [0.11.0|0.11.1|0.12.0|0.12.1] would require
│ │ └─ libgdal-core [>=3.10.3,<3.11.0a0 |>=3.12.0,<3.13.0a0 ], which can be installed (as previously explained);
│ └─ pyogrio 0.11.1 would require
│ └─ python >=3.14.0rc2,<3.15.0a0 but there are no viable options
│ ├─ python [3.14.0|3.14.1|3.14.2] conflicts with any installable versions previously reported;
│ └─ python [3.14.0rc2|3.14.0rc3] would require
│ └─ _python_rc, which does not exist (perhaps a missing channel);
├─ xz 5.4.7.* is not installable because it conflicts with any installable versions previously reported;
└─ zlib 1.3.1.* is not installable because it conflicts with any installable versions previously reported.
Pins seem to be involved in the conflict. Currently pinned specs:
- mkl==2024.2.2=arcgispro_14 (labeled as 'pin-1')
- python=3.13 (labeled as 'pin-2')
- protobuf=5.29.5 (labeled as 'pin-3')
- pro_notebook_integration=3.6 (labeled as 'pin-4')
- pillow=11.3 (labeled as 'pin-5')
- numpy=2.2 (labeled as 'pin-6')
- notebook=7 (labeled as 'pin-7')
- netcdf4=1.7.2 (labeled as 'pin-8')
- matplotlib=3.9.4 (labeled as 'pin-9')
- h5py=3.14.0 (labeled as 'pin-10')
- gdal=3.11.3 (labeled as 'pin-11')
- freetype=2.13 (labeled as 'pin-12')
- arcpy-base=3.6 (labeled as 'pin-13')
- arcpy=3.6 (labeled as 'pin-14')
- arcgispro=3.6 (labeled as 'pin-15')
- arcgis=2.4 (labeled as 'pin-16')

Re: Install "compatible" package in package manager failing

DanPatterson — Wed, 14 Jan 2026 13:24:27 GMT

"pinned" in the arcgispro-py3 or a clone of it means that trying to install a package that doesn't support the specs will potentially cause issues or failures. You can't use the package manager to try and install a package that isn't supported by conda, you will have to use the command line and a "pip" install

Package Manager—ArcGIS Pro | Documentation

and only try to do pip installs in your cloned environment.

Should things go bad, you can always "rollback" the failed install to a previous environment

Managing environments — conda 25.11.2.dev63 documentation

Re: Install "compatible" package in package manager failing

CordulaGöke — Wed, 14 Jan 2026 13:48:58 GMT

Somehow I am expecting that it will not work, if I change the pinned versions, but true, I can clone my clone and just try it out.

topic Re: Install "compatible" package in package manager failing in ArcGIS Pro Questions

Install "compatible" package in package manager failing

Re: Install "compatible" package in package manager failing

Re: Install "compatible" package in package manager failing