Issue #14660 has been updated by Adrien Thebo. Status changed from In Topic Branch Pending Review to Duplicate
#15346 dealt with similar behavior about the wrong gem repositories being used when installing, and the changes solved this problem as well. I am marking this ticket as a duplicate. ---------------------------------------- Bug #14660: package provider gem does not use the specified source if ensure => latest https://projects.puppetlabs.com/issues/14660#change-82811 Author: Evgeny Dudin Status: Duplicate Priority: Normal Assignee: Category: package Target version: Affected Puppet version: 2.7.14 Keywords: gem,latest,source Branch: https://github.com/puppetlabs/puppet/pull/809 I have a local gem repository where I put my gems. In the manifest I specify a package with ensure => latest and explicitly set the source <pre> class trocla { package { "moneta": ensure => "latest", provider => "gem", source => "http://mylocalrepo/gem-repository/";, } } </pre> In spite of that, puppet does not use my repo to fetch the list of available gems (which is confusing - if I explicitly specify my custom repository, I expect this package to be pulled from this particular repository). This can be seen in the output puppet with --debug option: `debug: Puppet::Type::Package::ProviderGem: Executing '/usr/bin/gem list --remote moneta$'` As you can see --source option is missing here -- 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.
