Bug 2319809

Summary:	Please branch and build python-django for EPEL 10
Product:	[Fedora] Fedora	Reporter:	Xavier Bachelot <xavier>
Component:	python-django5	Assignee:	Michel Lind <michel>
Status:	ASSIGNED ---	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	aekoroglu, mhroncok, michel, mrunge, python-packagers-sig, rdopiera, sgallagh, steve.traylen
Target Milestone:	---	Keywords:	FutureFeature
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:		Type:	---
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:	2303880, 2382036

Description Xavier Bachelot 2024-10-18 17:02:30 UTC

Hi,

Could you please branch and build python-django for EPEL 10 ?
It is needed to build another package.

Regards,
Xavier

Comment 1 Michel Lind 2024-11-13 23:50:14 UTC

Will do.

There's some refactor that needs to happen - we're going to basically switch to only providing versioned 'binary' packages for F42+ and RHEL 10 - but I do need to bring up the mailman stack for EPEL10 soon.

Comment 2 Steve Traylen 2025-02-17 20:01:04 UTC

Out of curiosity, what's a versioned binary package?

Comment 3 Michel Lind 2025-03-08 17:58:46 UTC

The built packages have the Django major version number as the suffix - so a) we can have multiple Django versions to select from, and b) we can unblock people who need the latest version without causing compatibility issues for those who need the older version (and decide whether to retire the old version separately once it has an unfixed security issue)