Why can't I install a Yum repository from RPM and then enable it?
Given a manifest like this, where I install a Yum repository RPM and then enable it with a yumrepo
resource, I'd expect it to end up with a usable package repository.
package { 'epel-release':
provider => rpm,
source => 'http://mirror.us.leaseweb.net/epel/6/i386/epel-release-6-8.noarch.rpm',
ensure => installed,
}
->
yumrepo { 'epel':
enabled => 1,
includepkgs => 'python-virtualenv python-pip', # others can conflict with asterisk
}
Instead, the final result is a Yum repo file that looks like
# cat /etc/yum.repos.d/epel.repo
[epel]
enabled=1
includepkgs=python-virtualenv python-pip
Obviously, that's not what I want. How can I make it work ...