Bug#1002065: scipy build-depenencies unsatisfiable in testing/unstable
On 2022-01-09 09:50, Laurent Bigonville wrote: On 9/01/22 00:43, Drew Parsons wrote: On 2022-01-08 19:44, Laurent Bigonville wrote: On Tue, 21 Dec 2021 11:09:02 + Peter Michael Green wrote: scipy build-depends on python3-pybind11 (<< 2.8) but testing and unstable have version 2.8.1-3 FTR, the package builds fine with python3-pybind11 2.9 ... So it should be safe to remove the upper bound for us. It's a pity apt-rdepends doesn't support reverse build-dependencies yet, it would make it simpler to keep track of these things when testing new releases. Thanks for your answer. Do you want me to upload the change? Or would you have time to do it? There's a new upstream release. I can do both at the same time. Drew
Bug#1002065: scipy build-depenencies unsatisfiable in testing/unstable
On 9/01/22 00:43, Drew Parsons wrote: On 2022-01-08 19:44, Laurent Bigonville wrote: On Tue, 21 Dec 2021 11:09:02 + Peter Michael Green wrote: scipy build-depends on python3-pybind11 (<< 2.8) but testing and unstable have version 2.8.1-3 FTR, the package builds fine with python3-pybind11 2.9 Could you drop that restriction or is it really broken with higher versions? They're conservative with their official releases. From scipy/pyproject.toml: "This to prevent that a future backwards-incompatible release will break the source build of a SciPy release.". It's more relevant for local user pip builds in a virtualenv, keeping the virtualenv constrained to known-good package versions. It's not so crucial for Debian since we maintain our own package self-consistency. In fact the upper bound is only applied upstream to the release versions. The development version has no upper bound (still set at "pybind11>=2.4.3") So it should be safe to remove the upper bound for us. It's a pity apt-rdepends doesn't support reverse build-dependencies yet, it would make it simpler to keep track of these things when testing new releases. Thanks for your answer. Do you want me to upload the change? Or would you have time to do it? Kind regards, Laurent Bigonville
Bug#1002065: scipy build-depenencies unsatisfiable in testing/unstable
On 2022-01-08 19:44, Laurent Bigonville wrote: On Tue, 21 Dec 2021 11:09:02 + Peter Michael Green wrote: scipy build-depends on python3-pybind11 (<< 2.8) but testing and unstable have version 2.8.1-3 FTR, the package builds fine with python3-pybind11 2.9 Could you drop that restriction or is it really broken with higher versions? They're conservative with their official releases. From scipy/pyproject.toml: "This to prevent that a future backwards-incompatible release will break the source build of a SciPy release.". It's more relevant for local user pip builds in a virtualenv, keeping the virtualenv constrained to known-good package versions. It's not so crucial for Debian since we maintain our own package self-consistency. In fact the upper bound is only applied upstream to the release versions. The development version has no upper bound (still set at "pybind11>=2.4.3") So it should be safe to remove the upper bound for us. It's a pity apt-rdepends doesn't support reverse build-dependencies yet, it would make it simpler to keep track of these things when testing new releases. Drew
Bug#1002065: scipy build-depenencies unsatisfiable in testing/unstable
On Tue, 21 Dec 2021 11:09:02 + Peter Michael Green wrote: > scipy build-depends on python3-pybind11 (<< 2.8) but testing and unstable > have version 2.8.1-3 FTR, the package builds fine with python3-pybind11 2.9 Could you drop that restriction or is it really broken with higher versions? Kind regards, Laurent Bigonville
Bug#1002065: scipy build-depenencies unsatisfiable in testing/unstable
Package: scipy Version: 1.7.1-2 Severity: serious scipy build-depends on python3-pybind11 (<< 2.8) but testing and unstable have version 2.8.1-3
