Bug 2367957

Summary:	Please branch and build python-jinja2 in EPEL 10
Product:	[Fedora] Fedora	Reporter:	Enrique <cquike>
Component:	python-jinja2	Assignee:	Thomas Moschny <thomas.moschny>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	42	CC:	code, orion, pj.pandit, python-packagers-sig, thomas.moschny
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-05-22 11:23:33 UTC	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:	2367955

Description Enrique 2025-05-22 10:33:10 UTC

Description of problem:

 Currently EPEL 10 repository doesn't include the jinja2 package. It would be very useful if that package is included in the EPEL 10 repository.

Thanks!


Reproducible: Always

Comment 1 Enrique 2025-05-22 11:16:39 UTC

I have just realized that there is a jinja2 package in the AlmaLinux 10 AppStream repository: https://vault.almalinux.org/10.0-beta/AppStream/x86_64/os/Packages/python3-jinja2-3.1.4-2.el10.noarch.rpm

I am not sure in that case whether EPEL needs to provide it or not, specially if other packages in EPEL depend on jinja2...

Comment 2 Ben Beasley 2025-05-22 11:23:33 UTC

See also https://tiny.distro.builders/view-rpm--view-c10s--python3-jinja2.html; python3-jinja2-3.1.6-1.el10 is indeed in AppStream (and python3-jinja2+i18n-3.1.6-1.el10 is in CRB).

Packages that are in AppStream or CRB repos are “in RHEL,” and are not eligible for EPEL. You’re expected to enable those repos instead. EPEL packages are built with both repos enabled.