coverage jobs fail with python-ligo-lw conflict
@adam-mercer @duncanmmacleod I'm seeing the latest coverage jobs failing, e.g. tonight's nightly but also on branches, with the following. Is this a regression in ligo-lw, or an unintentional premature upgrade to python 3.13 that we should block for the moment?
$ conda install --yes --quiet --name lalsuite-dev python-ligo-lw
Channels:
- conda-forge
- igwn
Platform: linux-64
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... warning libmamba Added empty dependency for problem type SOLVER_RULE_UPDATE
failed
LibMambaUnsatisfiableError: Encountered problems while solving:
- package python-ligo-lw-1.4.0-py27h14c3975_1000 requires python >=2.7,<2.8.0a0, but none of the providers can be installed
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;
└─ python-ligo-lw is not installable because there are no viable options
├─ python-ligo-lw [1.4.0|1.5.2|1.5.3|1.6.0] would require
│ └─ python >=2.7,<2.8.0a0 , which conflicts with any installable versions previously reported;
├─ python-ligo-lw [1.4.0|1.5.2|...|1.7.1] would require
│ └─ python >=3.6,<3.7.0a0 , which conflicts with any installable versions previously reported;
├─ python-ligo-lw [1.4.0|1.5.2|...|1.8.3] would require
│ └─ python >=3.7,<3.8.0a0 , which conflicts with any installable versions previously reported;
├─ python-ligo-lw [1.5.3|1.6.0|...|1.8.3] would require
│ └─ python >=3.8,<3.9.0a0 , which conflicts with any installable versions previously reported;
├─ python-ligo-lw [1.6.0|1.7.0|...|1.8.3] would require
│ └─ python >=3.9,<3.10.0a0 , which conflicts with any installable versions previously reported;
├─ python-ligo-lw [1.7.1|1.8.0|1.8.1|1.8.3] would require
│ └─ python >=3.10,<3.11.0a0 , which conflicts with any installable versions previously reported;
├─ python-ligo-lw 1.8.3 would require
│ └─ python >=3.11,<3.12.0a0 , which conflicts with any installable versions previously reported;
└─ python-ligo-lw 1.8.3 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')