Issue #18427 has been updated by Luke M.
Assignee set to Charlie Sharpsteen
Keywords set to gems provider
We do not have any custom written gems; all our gems originate from
rubygems.org. Our process is as follows:
o Retrieve gems from rubygems.org to gem repo:
gem fetch pupppet
o Tell repo about new gems
gem generate_index -d /path/to/gems
That is it. Hopefully that clears up any ambiguity.
More info here: http://docs.rubygems.org/read/chapter/18
----------------------------------------
Bug #18427: gem package provider updates gems even if the gem is already at the
latest revision
https://projects.puppetlabs.com/issues/18427#change-89208
* Author: Luke M
* Status: Needs More Information
* Priority: Normal
* Assignee: Charlie Sharpsteen
* Category: package
* Target version:
* Affected Puppet version: 2.7.20
* Keywords: gems provider
* 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.
