Jira (PUP-8664) rpm package provider is too specific

Vadym Chepkov (JIRA) Sun, 13 May 2018 19:52:57 -0700

Title: Message Title

Another situation where 'caching' brings unexpected results. RHEL7 supplies subversion version 1.7, which is old and we were asked to upgrade it. Wandisco provides their version of RPMs, but without separating libraries into a different RPM, like RedHat does, so we have to force uninstalling subversion-libs package before installing packages from Wandisco. Here is the code:

  yumrepo { 'wandisco':

    baseurl     => "http://opensource.wandisco.com/rhel/\$releasever/svn-${version}/RPMS/\$basearch",

    descr       => 'Wandisco Subversion',

    gpgcheck    => '1',

    gpgkey      => 'http://opensource.wandisco.com/RPM-GPG-KEY-WANdisco',

    includepkgs => 'mod_dav_svn serf libserf subversion*',

  # RHEL library conflicts with wandisco binary

  package { 'subversion-libs':

    ensure => purged,

  package { ['mod_dav_svn', 'subversion']:

    ensure  => latest,

    require => [Yumrepo['wandisco'],Package['subversion-libs']],

To my big surprise, after puppet run I end up without mod_dav_svn or subversion of a any version.
Only second run will put proper packages back.

Add Comment

This message was sent by Atlassian JIRA

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8664) rpm package provider is too specific

Reply via email to