Bug 2059975

Summary:	python-fasjson-client fails to build with pytest 7, pins pytest to < 7
Product:	[Fedora] Fedora	Reporter:	Miro Hrončok <mhroncok>
Component:	python-fasjson-client	Assignee:	Nils Philippsen <nphilipp>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	infra-sig, nphilipp
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-fasjson-client-1.0.7-1.fc37	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-17 15:47:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2045102, 2050629

Description Miro Hrončok 2022-03-02 12:29:54 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 python-fasjson-client-0:1.0.5-1.fc36.src fails to build because it pins pytest to < 7.

(python3.10dist(pytest) >= 4.6.11 with python3.10dist(pytest) < 7)


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

I'(ve also reported this in https://github.com/fedora-infra/fasjson-client/issues/233 but there was no response either :(



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. If you need specific help, let me know.

Thanks!

Comment 1 Nils Philippsen 2022-05-17 15:47:58 UTC

Hey Miro,

sorry I didn't respond earlier! I need to get my legacy items in order… this means both components I worked heavily at some point and ended up as the main admin, as well as my communications (which are a mess frankly, the mail filtering of you-know-who around which I can't get my head wrapped around since being forced to use it is a quite effective black hole for any ticket-related email here). Again, sorry for the disappointment – please poke me directly if things slip under my radar again, thanks!

Anyway, version 1.0.7 built fine only last week, so I'll close this one.