On 3/22/22 18:20, Axel Braun wrote:
Am Dienstag, 22. März 2022, 01:55:36 CET schrieb Simon Lees:
On 3/22/22 07:07, Axel Braun wrote:
Am Montag, 21. März 2022, 21:32:14 CET schrieb Matěj Cepl:
Dne 21. 03. 22 v 10:47 Axel Braun napsal(a):
python-appdirs 1.4.4 python-backports.entry_points_selectable 1.1.1 python-importlib-metadata 4.10.1 python-iniconfig 1.1.1 python-mypy 0.941 python-mypy_extensions 0.4.3 python-packaging 21.3 python-platformdirs 2.4.0 python-py 1.11 python-pytest 6.2.5 python-pytest-isort 1.1.0 (fix build error for python-pydyf) python-pytest-mock 3.6.1 python-pytest-mypy 0.8.1 python-pytest-xdist 2.5.0 python-setuptools 58.3.0 python-setuptools_scm 6.4.2 python-sphinx-autodoc-typehints 1.12 python-virtualenv 20.13.3
And now remove from that project all packages which are already in SLE-15. There is just no way you would be allowed to upgrade setuptools packaging, mypy, importlib-metadata, or pytest, or anything else which is already in SLE-15. What exact reasons you have for these upgrades?
The versions in SLE are simply too old!
This really doesn't tell us anything, what we need to know is "Why are they too old?" Some upstreams set there minimum version requirements based on what they test, in which case they may not actually be too old and we are fine. Some upstreams bump the minimum version because they know there are bugs that are fixed in the newer versions, in which case in most cases we can just backport the bugfixes to the older versions without too much issue.
My procedure was to determine the unresovleables, and from there take the latest available version, resp, the latest version that supports Python 3.6
Your proposal is to take the least required version.
Not quite, it is to take the version we already have and make it work.
Is this approach better? Not necessarily. You miss fixes and new functionality. Is it less effort? Maybe.
For your convenience, I have disabled all builds for the mentioned packages and cleaned out the binaries, so we are back at start:
python-tinydb: nothing provides python3-pytest-mypy
python-pytest-mypy (0.8.1): nothing provides python3-mypy >= 0.900, (got version 0.670 provided by mypy) nothing provides python3-mypy_extensions >= 0.4.3 needed by python3-mypy, (got version 0.4.1-bp154.1.9) python3-mypy_extensions (0.4.3) (builds)
pyton3-mypy (0.941): nothing provides python3-importlib-metadata >= 4.6.1, (got version 1.5.0-3.3.5), nothing provides python3-pytest >= 6.2, (got version 5.4.3-150400.1.2), (got version 5.4.3-1.24 provided by python3-pytest5), (got version 4.6.9-3.3.4 provided by python3-pytest4), nothing provides python3-pytest-xdist >= 1.34, (got version 1.32.0-150400.1.2), nothing provides python3-virtualenv >= 20.6, (got version 16.1.0-1.13)
And so on.
Yeah so the next step would be to just require everything without the version numbers, but I agree with Ben and we should probably try and make tinydb work without pytest-mypy as a starting point.
If you let me know your user in OBS, I add you as maintainer and you can try to find out the lowest needed version (branch-in packages with different name)
https://build.opensuse.org/users/simotek -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B