Issue #18427 has been updated by Charlie Sharpsteen.
Luke M wrote: > The gems are from rubygems.org. If you don't specify the source you don't see > the problem. If you specify `--source`, then the gems are no longer entirely from rubygems.org---you also get gems from `http://puppet:8808`. So, the question still remains: where did the gems on `http://puppet:8808` come from? If they were custom built, was ` ruby` added to the end of the version string? ---------------------------------------- Bug #18427: gem package provider updates gems even if the gem is already at the latest revision https://projects.puppetlabs.com/issues/18427#change-89092 * Author: Luke M * Status: Needs More Information * Priority: Normal * Assignee: * Category: package * Target version: * Affected Puppet version: 2.7.20 * Keywords: * Branch: ---------------------------------------- Using: package{'facter': ensure => latest, provider => 'gem', source => "http://puppet:8808";, } Produces: notice: /Stage[main]/Common_puppet::Hpux/Package[facter]/ensure: ensure changed '1.6.17' to '1.6.17 ruby' This happens on every puppet run. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- 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 http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
