Bug 804829

Summary: Package is mis-named
Product: [Fedora] Fedora EPEL Reporter: Thomas S Hatch <thatch45>
Component: python-jinja2Assignee: Luke Macken <lmacken>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: el6CC: lmacken, pfrields, pj.pandit, thomas.moschny
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-19 21:30:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Thomas S Hatch 2012-03-19 21:02:51 UTC
Description of problem:
The python-jinja2 package is named python-jinja2-26 in EPEL for RHEL 6
http://dl.fedoraproject.org/pub/epel/6/x86_64/repoview/python-jinja2-26.html

If i am not mistaken it should be named python-jinja2, this is what the deps for the package are looking for, all packages in EPEL that require python-jinja2 have broken deps

Comment 1 Thomas Moschny 2012-03-19 21:30:20 UTC
(In reply to comment #0)
> Description of problem:
> The python-jinja2 package is named python-jinja2-26 in EPEL for RHEL 6
> http://dl.fedoraproject.org/pub/epel/6/x86_64/repoview/python-jinja2-26.html
> 
> If i am not mistaken it should be named python-jinja2, this is what the deps
> for the package are looking for, all packages in EPEL that require
> python-jinja2 have broken deps

You are confusing two packages:
 * python-jinja2 is not part of EPEL6, because it is in one of RHEL6 channels
 * python-jinja2-26 is in EPEL6, and is the Jinja2 package for Python 2.6.