Re: [ansible-project] Installing via 'sudo yum install ansible' on REL 6.3 results in 'Requires: python-jinja2'

[Daniel Hokka Zakrisson]

John Krewson wrote:
> Greetings,
>
> I have looked through this group and found some questions similar to mine,
> but the posts I found were from some months ago and I can't quite tell if
> there is a problem with a reference in the Epel ansible package or if I'm
> performing a step incorrectly. If I need to ask the Epel maintainers
> instead, please let me know.
>
> On a REL 6.3 server, I have access to the Epel 6 list of packages. Epel 6
> contains an 'ansible' package.
>
> When attempting to install, I get the following:
>
> Error: Package: ansible-0.8-1.el6.noarch (epel-rhel6-x86_64)
> Requires: python-jinja2
>
> Epel 6 has python-jinja2-26, but the ansible package is referring to the
> jinja2 package in Epel 5.
>
> Has anyone run into this before? I've included some addition details of my
> setup at the end of the message.

You have to enable the RHEL6 optional channel to get it. It's not in EPEL.

Daniel

[Michael DeHaan]

It is in EPEL.

http://dl.fedoraproject.org/pub/epel/6/x86_64/repoview/python-jinja.html

It looks like the "-26" version is just a noarch package pointing to the other.

[Daniel Hokka Zakrisson]

python-jinja is not Jinja2, it is the old Jinja1. The -26 version is for
Jinja2 version 2.6, instead of the 2.2 that is in RHEL.

Daniel

[Michael DeHaan]

On Wed, Feb 27, 2013 at 3:44 PM, Daniel Hokka Zakrisson

Ha, ok, so they completely renamed things or I've just been using pip.

This is totally fixable through a conditional in the specfile.

Cobbler does some of this and we can port it.

https://github.com/cobbler/cobbler/blob/master/cobbler.spec

The question is, how was it *already* working in EPEL6 and not failing
or was this a recent rename in EPEL (and if so, not cool, EPEL?)

Adding Tim on CC in case he knows.







==

[Michael DeHaan]

Ok, so it sounds like python-jinja2 does NOT need to be in there for
CentOS EPEL because it's already in CentOS CentOS, so this is just
what Daniel said about enabling the other RHEL repo.

Computers are hard! :)

[John Krewson]

I will check that out. I thought it was a missed inclusion. Thanks!

[Kashyap Bhatt]

I had the same issue, I found python-jinja2 in "Optional" repo.
Then I had some issues with public key of the package, which were solved (read ignored) by adding --nogpgcheck to yum install.

Entry from /etc/yum.repos.d/rhel.repo:

[Optional]
name=Red Hat Enterprise Linux $releasever $basearch - Optional
baseurl=http://mrepo.dev.sabre.com/$releasever-$basearch/RPMS.optional
enabled=0
gpgcheck=1
file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release


Command that worked for me:
root@XXX# yum --enablerepo=Optional --nogpgcheck install  python-jinja2.x86_64
could also be, which should resolve the dependency now:
root@XXX# yum --enablerepo=Optional --nogpgcheck install ansible

Alternately you could also:
* set enabled=1 in /etc/yum.repos.d/rhel.repo for this repo instead of --enablerepo=Optional on command line to yum
* set gpgcheck=0 in /etc/yum.repos.d/rhel.repo for this repo (OR install the key using rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release) instead of --nogpgcheck

Source: http://www.linuxquestions.org/questions/fedora-35/public-key-not-installed-468615/