zebbecker
commented
3 days ago Looks like scalene pins just conflict with 3.13
fresh) root@workspacem0onea65hvi4h21y:~# conda install scalene
Channels:
- conda-forge
Platform: linux-64
Collecting package metadata (repodata.json): done
Solving environment: \ warning libmamba Added empty dependency for problem type SOLVER_RULE_UPDATE
failed
LibMambaUnsatisfiableError: Encountered problems while solving:
- nothing provides _python_rc needed by python-3.12.0rc3-rc3_hab00c5b_1_cpython
Could not solve for environment specs
The following packages are incompatible
├─ pin-1 is installable and it requires
│ └─ python 3.13.* , which can be installed;
└─ scalene is not installable because there are no viable options
├─ scalene [1.5.10|1.5.11|...|1.5.41] would require
│ └─ python >=3.10,<3.11.0a0 , which conflicts with any installable versions previously reported;
├─ scalene [1.5.10|1.5.11|...|1.5.34] would require
│ └─ python >=3.8,<3.9.0a0 , which conflicts with any installable versions previously reported;
├─ scalene [1.5.10|1.5.11|...|1.5.41] would require
│ └─ python >=3.9,<3.10.0a0 , which conflicts with any installable versions previously reported;
├─ scalene [1.5.13|1.5.14|...|1.5.41] would require
│ └─ python >=3.11,<3.12.0a0 , which conflicts with any installable versions previously reported;
├─ scalene 1.5.31.1 would require
│ └─ python >=3.12.0rc3,<3.13.0a0 but there are no viable options
│ ├─ python [3.12.0|3.12.1|...|3.12.7] conflicts with any installable versions previously reported;
│ └─ python 3.12.0rc3 would require
│ └─ _python_rc, which does not exist (perhaps a missing channel);
└─ scalene [1.5.31.1|1.5.33.1|...|1.5.41] would require
└─ python >=3.12,<3.13.0a0 , which conflicts with any installable versions previously reported.
Pins seem to be involved in the conflict. Currently pinned specs:
- python 3.13.* (labeled as 'pin-1')
Python 3.13 was released last week. Our run_dps_build.sh script was installing 3.13 during the DPS image build process, and some interaction between that and our requirements (scalene?) causes the DPS image build to fail. This is reproducible on ADE as of today.
to reproduce:
error trace from DPS image build: