Hello,
the pytest package (python3-pytest) has been updated to 5.4.2.
In case it gives you trouble, you can pin an older version:
BuildRrequires: %{py3_dist pytest} < 5
Or:
BuildRrequires: python3dist(pytest) < 5
That will give you the python3-pytest4 package (4.6.10 now), not parallely installable with python3-pytest.
Note that the python3-pytest4 package is deprecated, but no removal date has been set. Likely, it will get orphaned or retired when no important packages need it.
The pytest 4.6.x series is still being occasionally released, but:
https://docs.pytest.org/en/latest/py27-py34-deprecation.html#maintenance-of-...
"From now on, the core team will no longer actively backport patches, but the 4.6.x branch will continue to exist so the community itself can contribute patches."
Side note: The Fedora 31/32 python3-pytest package does not provide python3-pytest4, hence I recommend not to BuildRequire python3-pytest4 directly by name, but using python3dist(pytest) or %py3_dist as in the examples above.
On 29. 05. 20 17:57, Miro Hrončok wrote:
Hello,
the pytest package (python3-pytest) has been updated to 5.4.2.
In case it gives you trouble, you can pin an older version:
BuildRrequires: %{py3_dist pytest} < 5
Or:
BuildRrequires: python3dist(pytest) < 5
That will give you the python3-pytest4 package (4.6.10 now), not parallely installable with python3-pytest.
Note that the python3-pytest4 package is deprecated, but no removal date has been set. Likely, it will get orphaned or retired when no important packages need it.
The pytest 4.6.x series is still being occasionally released, but:
https://docs.pytest.org/en/latest/py27-py34-deprecation.html#maintenance-of-...
"From now on, the core team will no longer actively backport patches, but the 4.6.x branch will continue to exist so the community itself can contribute patches."
Side note: The Fedora 31/32 python3-pytest package does not provide python3-pytest4, hence I recommend not to BuildRequire python3-pytest4 directly by name, but using python3dist(pytest) or %py3_dist as in the examples above.
For this very reason, the following packages might want to switch to not require python3-ptest by name:
$ repoquery --repo=rawhide --whatrequires python3-pytest --exact copr-keygen-0:1.77-1.fc32.noarch hatch-0:0.23.0-2.fc32.noarch python3-astropy-0:4.0.1.post1-1.fc33.x86_64 python3-conu-pytest-0:0.7.1-8.fc32.noarch python3-django-pytest-0:0.2.0-24.fc32.noarch python3-gabbi-0:1.49.0-1.fc32.noarch python3-ipatests-0:4.8.6-1.fc33.noarch python3-ipyparallel-tests-0:6.3.0-1.fc33.noarch python3-ipython-tests-0:7.14.0-1.fc33.noarch python3-lib389-0:1.4.4.2-1.fc33.1.noarch python3-metakernel-tests-0:0.24.4-1.fc33.noarch python3-pyfakefs-0:3.5.8-5.fc32.noarch python3-pytest-arraydiff-0:0.3-5.fc32.noarch python3-pytest-astropy-0:0.5.0-4.fc32.noarch python3-pytest-asyncio-0:0.10.0-5.fc32.noarch python3-pytest-beakerlib-0:0.7.1-12.fc32.noarch python3-pytest-benchmark-0:3.2.3-1.fc33.noarch python3-pytest-cache-0:1.0-21.fc33.noarch python3-pytest-capturelog-0:0.7-19.fc32.noarch python3-pytest-doctestplus-0:0.3.0-5.fc32.noarch python3-pytest-faulthandler-0:1.6.0-5.fc32.noarch python3-pytest-forked-0:1.1.1-2.fc32.noarch python3-pytest-httpbin-0:0.3.0-11.fc32.noarch python3-pytest-mock-0:1.10.4-7.fc32.noarch python3-pytest-openfiles-0:0.3.2-5.fc32.noarch python3-pytest-relaxed-0:1.1.5-7.fc32.noarch python3-pytest-remotedata-0:0.3.1-5.fc32.noarch python3-pytest-runner-0:4.0-9.fc32.noarch python3-pytest-sourceorder-0:0.5-17.fc32.noarch python3-pytest-spec-0:2.0.0-2.fc32.noarch python3-pytest-testmon-0:0.9.19-2.fc32.noarch python3-pytest-timeout-0:1.3.4-2.fc32.noarch python3-pytest-vcr-0:1.0.2-5.fc32.noarch python3-pytest-virtualenv-0:1.7.0-6.fc32.noarch python3-pytest-watch-0:4.2.0-5.fc32.noarch python3-pytest-xdist-0:1.32.0-1.fc33.noarch python3-qcelemental-0:0.12.0-3.fc32.noarch python3-rustcfg-tests-0:0.0.2-6.fc32.noarch python3-tinyrpc-tests-0:1.0.3-2.fc32.noarch
On Fri, May 29, 2020 at 4:58 PM Miro Hrončok mhroncok@redhat.com wrote:
Hello,
the pytest package (python3-pytest) has been updated to 5.4.2.
In case it gives you trouble, you can pin an older version:
BuildRrequires: %{py3_dist pytest} < 5
Or:
BuildRrequires: python3dist(pytest) < 5
That will give you the python3-pytest4 package (4.6.10 now), not parallely installable with python3-pytest.
Note that the python3-pytest4 package is deprecated, but no removal date has been set. Likely, it will get orphaned or retired when no important packages need it.
The pytest 4.6.x series is still being occasionally released, but:
https://docs.pytest.org/en/latest/py27-py34-deprecation.html#maintenance-of-...
"From now on, the core team will no longer actively backport patches, but the 4.6.x branch will continue to exist so the community itself can contribute patches."
Side note: The Fedora 31/32 python3-pytest package does not provide python3-pytest4, hence I recommend not to BuildRequire python3-pytest4 directly by name, but using python3dist(pytest) or %py3_dist as in the examples above.
-- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok
When running the fedora-review tool on a package that has "BuildRequires: python3dist(pytest)" in it (note there is no version dependency on the pytest package), the review is complaining that:
- Package must not depend on deprecated() packages. Note: python3-pytest4 is deprecated, you must not depend on it.
Looking in the build log, it is actually using pytest5 though:
+ /usr/bin/python3 -m pytest ============================= test session starts ============================== platform linux -- Python 3.9.0b1, pytest-5.4.2, py-1.8.0, pluggy-0.13.0
I have already cleaned my mock cache, and ran mock --scrub=all and this persists. Is there another cache that has to be cleaned, or a package that needs updating?
-Ian
On 31. 05. 20 14:06, Ian McInerney wrote:
On Fri, May 29, 2020 at 4:58 PM Miro Hrončok <mhroncok@redhat.com mailto:mhroncok@redhat.com> wrote:
Hello, the pytest package (python3-pytest) has been updated to 5.4.2. In case it gives you trouble, you can pin an older version: BuildRrequires: %{py3_dist pytest} < 5 Or: BuildRrequires: python3dist(pytest) < 5 That will give you the python3-pytest4 package (4.6.10 now), not parallely installable with python3-pytest. Note that the python3-pytest4 package is deprecated, but no removal date has been set. Likely, it will get orphaned or retired when no important packages need it. The pytest 4.6.x series is still being occasionally released, but: https://docs.pytest.org/en/latest/py27-py34-deprecation.html#maintenance-of-4-6-x-versions "From now on, the core team will no longer actively backport patches, but the 4.6.x branch will continue to exist so the community itself can contribute patches." Side note: The Fedora 31/32 python3-pytest package does not provide python3-pytest4, hence I recommend not to BuildRequire python3-pytest4 directly by name, but using python3dist(pytest) or %py3_dist as in the examples above. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncokWhen running the fedora-review tool on a package that has "BuildRequires: python3dist(pytest)" in it (note there is no version dependency on the pytest package), the review is complaining that:
- Package must not depend on deprecated() packages.
Note: python3-pytest4 is deprecated, you must not depend on it.
Looking in the build log, it is actually using pytest5 though:
- /usr/bin/python3 -m pytest
============================= test session starts ============================== platform linux -- Python 3.9.0b1, pytest-5.4.2, py-1.8.0, pluggy-0.13.0
I have already cleaned my mock cache, and ran mock --scrub=all and this persists. Is there another cache that has to be cleaned, or a package that needs updating?
No, this is a bug in fedora-review.
https://pagure.io/FedoraReview/issue/392
python-devel@lists.fedoraproject.org
-
Ian McInerney -
Miro Hrončok