I am having trouble updating the arcgis module in my cloned environment. I have not had issues using the package manager in Pro to install or update packages.
Currently have Pro 3.1.3 and arcgis 2.1.0.2. The package manager notes that updates are available, I click 'update all,' I get a happy green check saying updates complete....but then none of the packages are updated.
I have tried to install the new version of arcgis from the command line but it says it cannot due to 'pinned specs.'
(arcgispro-py3-clone) C:\Users\tbott\AppData\Local\ESRI\conda\envs\arcgispro-py3-clone>conda install -c esri arcgis=2.2.0.1
Collecting package metadata (current_repodata.json): done
Solving environment: \ WARNING conda.core.solve:_add_specs(648): pinned spec arcgis=2.1.0 conflicts with explicit specs. Overriding pinned spec.
failed with initial frozen solve. Retrying with flexible solve.
Solving environment: - WARNING conda.core.solve:_add_specs(648): pinned spec arcgis=2.1.0 conflicts with explicit specs. Overriding pinned spec.
failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: / WARNING conda.core.solve:_add_specs(648): pinned spec arcgis=2.1.0 conflicts with explicit specs. Overriding pinned spec.
failed with initial frozen solve. Retrying with flexible solve.
Solving environment: | WARNING conda.core.solve:_add_specs(648): pinned spec arcgis=2.1.0 conflicts with explicit specs. Overriding pinned spec.
failed
SpecsConfigurationConflictError: Requested specs conflict with configured specs.
requested specs:
- arcgis=2.2.0.1
- arcpy-base=3.1
- esri/win-64::arcpy==3.1=py39_arcgispro_41759
- proj4
pinned specs:
- mkl==2020.0=arcgispro_167
- numpy=1.20
Use 'conda config --show-sources' to look for 'pinned_specs' and 'track_features'
configuration parameters. Pinned specs may also be defined in the file
C:\Users\tbott\AppData\Local\ESRI\conda\envs\arcgispro-py3-clone\conda-meta\pinned.
The output gives the location of the pinned file. Is it safe to update this manually? What is the best way to get the version updated? I do not have admin rights on my machine so I cannot myself update to Pro 3.2, if that's the solution. Or is this a conda problem?
