Bug 2224723

Summary:	[RFE:EPEL9] Update python-hatchling and python-hatch-vcs
Product:	[Fedora] Fedora EPEL	Reporter:	Martin Hoyer <mhoyer>
Component:	python-hatchling	Assignee:	Ben Beasley <code>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel9	CC:	code, lbalhar, python-packagers-sig
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-24 01:21:51 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:

Description Martin Hoyer 2023-07-22 14:13:01 UTC

Description of problem:
hatchling on EPEL9 is stuck on version 0.25, while Fedora>=37 is on 1.16.

This, alongside with older version of hatch-vcs for example means el9 builds are not able to take advantage of pyproject_buildrequires macro when using hatch-vcs.

Comment 1 Ben Beasley 2023-07-24 01:21:51 UTC

Sorry, I know this is inconvenient, but EL9 has been out quite a bit longer than hatchling/hatch 1.x, and last time I looked at this I concluded that that the packages in the base OS were too old to satisfy the dependency requirements of a newer version. See https://bugzilla.redhat.com/show_bug.cgi?id=2158497#c2 for details.

If you really think I’ve missed something, I’m happy to consider a PR.

Meanwhile, you should still be able to use %pyproject_buildrequires in EPEL9 if you add the “-w” option. Note that you will also always have to explicitly mark license files with %license, even if %pyproject_files handles them automagically in current Fedora releases.

*** This bug has been marked as a duplicate of bug 2158497 ***

Comment 2 Martin Hoyer 2023-07-24 14:21:41 UTC

Thank You for the prompt reply Ben!
I'm sorry I didn't spot the original bz and opened a dup.

Let me do a comment in #2158497