Issue #16997 has been updated by Andrew Parker. Status changed from Unreviewed to Duplicate
It sounds like what you are expecting to happen is that puppet picks up the modified environment after the ruby install has happened. This looks to be that same as the underlying issue in #16048. I'm marking this as a duplicate of that issue. ---------------------------------------- Bug #16997: Puppet gem provider on windows does not work as expected https://projects.puppetlabs.com/issues/16997#change-73773 Author: Luis Mayorga Status: Duplicate Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: Hi, I just installed ruby1.9.3.exe package on a windows build server and also i was thinking on installing some gems. It seems that is installing the gems as part as as the 1.8.7 ruby version shipped with the Puppet Client windows installer. <pre> class ruby{ file {'ruby': name => 'C:\Temp\rubyinstaller-1.9.3-p194.exe', ensure => present, source => 'V:\shardata\Puppet\rubyinstaller-1.9.3-p194.exe' } exec { 'ruby': command => 'C:\Temp\rubyinstaller-1.9.3-p194.exe /verysilent /dir="C:\ruby" /tasks="assocfiles,modpath"', require => File["ruby"] } # package { 'nokogiri': # ensure => '1.5.5', # provider => 'gem', # require => Exec['ruby'] # } </pre> Should I still use the gem provider or should i use the exec and map the new ruby package gem.bat path. -- 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 post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
