Bug 2059980 - python3-pytest-testmon fails to install with pytest 7, pins pytest to < 7
Summary: python3-pytest-testmon fails to install with pytest 7, pins pytest to < 7
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: python-pytest-testmon
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Radez
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTEST7
TreeView+ depends on / blocked
 
Reported: 2022-03-02 12:33 UTC by Miro Hrončok
Modified: 2022-03-02 14:23 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-03-02 14:09:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Miro Hrončok 2022-03-02 12:33:24 UTC
In this copr repo, I have updated pytest to 7.0.1:

https://copr.fedorainfracloud.org/coprs/churchyard/pytest-7/

Based on this PR:

https://src.fedoraproject.org/rpms/pytest/pull-request/25

I'd like to update pytest to 7 in Fedora 37, but this package fails to install because it pins pytest to < 7.


python3-pytest-testmon-0:1.2.2-2.fc36.noarch
(python3.10dist(pytest) < 7~~ with python3.10dist(pytest) >= 5)


I've been trying to reach you in the PR since half-December but there was no response, hence opening this bugzilla.


There are several packages affected by this update, so I'd very much appreciate it if you could try to relax this requirement (preferably upstream) and fix any problems with that. Please, check if your upstream hasn't already fixed it and backport the fix if possible. Report this failure to your upstream otherwise. If you need specific help, let me know.

Thanks!

Comment 1 Dan Radez 2022-03-02 14:09:39 UTC
this package was updated to 1.3.0 in rawhide yesterday.
It looks like the requirement was update to <8 upstream in this release:

setup.cfg:	pytest>=5,<8

I believe this bz was fixed yesterday's update.

Comment 2 Miro Hrončok 2022-03-02 14:23:50 UTC
Awesome, sorry for the noise.


Note You need to log in before you can comment on or make changes to this bug.