Bug 460092

Summary:	python-jinja branch for EPEL-5
Product:	[Fedora] Fedora	Reporter:	Toshio Ernie Kuratomi <a.badger>
Component:	python-jinja	Assignee:	Thomas Moschny <thomas.moschny>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	tkuratom
Target Milestone:	---	Flags:	a.badger: fedora-cvs+
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-09-24 15:50:17 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:

Description Toshio Ernie Kuratomi 2008-08-26 05:23:04 UTC

Hi, I'm trying to get python-sphinx built for EPEL-5 and need to have python-jinja to make that a reality.  Are you interested in branching python-jinja for EPEL-5?

Comment 1 Thomas Moschny 2008-08-26 16:00:36 UTC

Yeah, why not.

However, either having a, or being a co-maintainer for the EPEL branch wouldn't be that bad, as I currently don't have any packages in EPEL.

How to proceed? Can I make a CVS request here, in that bug?

Comment 2 Toshio Ernie Kuratomi 2008-08-26 16:10:59 UTC

Yep, just fill out the CVS request template and set the fedora-cvs flag to "?".

I'll request to be a comaintainer in the pkgdb since I'll be using this quite a lot via sphinx.

Thanks!

Comment 3 Thomas Moschny 2008-08-26 16:16:38 UTC

Package Change Request
======================
Package Name: python-jinja
New Branches: EL-5

Comment 4 Toshio Ernie Kuratomi 2008-08-26 16:43:09 UTC

cvs done.

Comment 5 Thomas Moschny 2008-09-24 15:29:07 UTC

Can we close this bug then?

Comment 6 Toshio Kuratomi 2008-09-24 15:50:17 UTC

Yep.  Thanks for branching this!