On Fri, 2019-08-23 at 11:13 +0200, Thomas Bechtold wrote:
Hi,
python-tornado broke now the cloud ci[1]:
nothing provides python2-tornado-impl = 4.5.3 needed by python2-tornado
I don't understand why the python-tornado package is now an empty package (instead of just packaging the latest version).
Can't we have:
- python-tornado (which is tornado6) - python-tornado5 (which is tornado5) - python-tornado4 (..)
and if a package requires something different from the latest version, just adjust the Requires: there? That seems to be the way we go with python-pytest and I don't see a reason why to not follow that.
Am I missing something here?
That is one valid approach - and the tornado maintainer chose the 2nd on - same as is used by go, gcc and others. They have a meta package which gives the 'preferred' version of a package for the distribution (non-suffixed) - and all the others, including the actual code to the meta package, as a suffixed package. python-tornado4 with the correct version has been checked in to Factory the exact same moment as python-tornado requiring it. Cheers Dominique