Bug 2144665

Summary:	Please branch and build python-jinja2 in epel9
Product:	[Fedora] Fedora	Reporter:	Jonathan Wright <jonathan>
Component:	python-jinja2	Assignee:	Thomas Moschny <thomas.moschny>
Status:	CLOSED CANTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	38	CC:	carl, lewk, mhroncok, orion, pj.pandit, python-packagers-sig, thomas.moschny
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-02-11 05:34:53 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:	2032550

Description Jonathan Wright 2022-11-22 00:31:32 UTC

Please branch and build python-jinja2 in epel9.

If you do not wish to maintain python-jinja2 in epel9,
or do not think you will be able to do this in a timely manner,
the EPEL Packagers SIG would be happy to be a co-maintainer of the package;
please add the epel-packagers-sig group through
https://src.fedoraproject.org/rpms/python-jinja2/addgroup
and grant it commit access, or collaborator access on epel* branches.

I would also be happy to be a co-maintainer (FAS: jonathanspw).

I can be the primary contact for EPEL (FAS: jonathanspw).

Comment 1 Thomas Moschny 2022-12-03 12:14:17 UTC

There already exists a python3-jinja2 package in appstream 9.x/9s, so we can't simply branch and build. This is version 2.11.3, though.

So, as the request really is about >=3, we'd need to make an EPEL9-only package python3-jinja2-31 or similar, I guess. Will have a look how that works nowadays.

Comment 2 Miro Hrončok 2023-01-25 13:20:12 UTC

> we'd need to make an EPEL9-only package python3-jinja2-31 or similar, I guess. Will have a look how that works nowadays.

Note that the package would conflict (on files level) with python3-jinja and conflicts with RHEL are not allowed in EPEL unfortunately.

Comment 3 Ben Cotton 2023-02-07 15:11:21 UTC

This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle.
Changing version to 38.

Comment 4 Carl George 🤠 2023-02-11 05:34:53 UTC

There isn't really a feasible solution for this.  The real answer will be dropping the pandas version being packaged for EPEL 9 to a version that is compatible with the version of jinja2 that in RHEL 9 AppStream.