Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Thomas Kishel commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Thank you for fixing this in PUP-10677 !!! Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.125405.1459986358000.154518.1614640320035%40Atlassian.JIRA.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Thomas Kishel commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows I defer to a principle engineer about principles That's reasonable, especially if we actually fix this in P7. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.125405.1459986358000.95092.1568246700678%40Atlassian.JIRA.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Josh Cooper commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows How about: puppet_gem provider installs into Puppet gem provider installs into system ruby Caveat: The gem provider on Windows installs into Puppet's ruby. To manage gems in system ruby, specify the path to gem.cmd as the command parameter. In Puppet 7, the behavior will be changed so it's not necessary. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.125405.1459986358000.94952.1568242200887%40Atlassian.JIRA.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Thomas Kishel commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows I realize this may be a matter of principle ... but I'm imagining trying to explain this to a user in documentation or a support ticket. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.125405.1459986358000.93042.1568160300714%40Atlassian.JIRA.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Thomas Kishel commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Yes but it is counterintuitive that ... On Windows, the gem provider installs into Puppet On Linux, the gem provider installs into system Ruby On both Linux and Windows, the puppet_gem provider installs into Puppet Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.125405.1459986358000.93024.1568160120533%40Atlassian.JIRA.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title
Josh Cooper commented on PUP-6134
Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
I made a note in the PR, I think we can close this ticket as a dup of PUP-6488 and close the PR. Using the new targetable functionality it's possible to manage gems on windows (and other platforms) for ruby installations different than the vendored ruby in our puppet-agent package: I installed chocolatey using:
C:\Users\Administrator>choco install ruby
...
Ruby is going to be installed in 'C:\tools\ruby26'
Installing 64-bit ruby...
...
Then installed the gem into that ruby using:
package { 'puppet-lint':
ensure => present,
provider => 'gem',
command => 'C:\tools\ruby26\bin\gem.cmd',
}
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Mihai Buzgau Sprint: NW - 2019-08-21, NW - 2019-09-03 , NW - 2019-09-18 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.125405.1459986358000.84568.1567588623761%40Atlassian.JIRA.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Mihai Buzgau Sprint: NW - 2019-08-21 , NW - 2019-09-03 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.125405.1459986358000.65441.1566379024144%40Atlassian.JIRA.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Thomas Kishel commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows I remember there being a concern with this change similar to "but what about users who depend on this bug to mange Puppet Ruby gems (instead of using the puppet_gem provider" but I don't thank that is common or valid, and they have/should use the the puppet_gem provider. BTW: I've implemented Ethan's recommendation on 2017/01/04 3:09 PM via the command attribute in PUP-6488. I'm writing acceptance tests for PUP-8949 now, and once those are complete, I'll re-review this and add a test for this ... Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.125405.1459986358000.55547.1565793420682%40Atlassian.JIRA.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.125405.1459986358000.55308.1565784902415%40Atlassian.JIRA.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Mihai Buzgau Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.125405.1459986358000.46111.1565168461442%40Atlassian.JIRA.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Mihai Buzgau Sprint: PR NW - Triage 2019-08-21 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.125405.1459986358000.46126.1565168461522%40Atlassian.JIRA.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Mihai Buzgau Sprint: PR - Triage Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.125405.1459986358000.36124.1564500480580%40Atlassian.JIRA.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Team: Platform OS Puppet Romania Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.125405.1459986358000.54344.1560984421306%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Thomas Kishel commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows https://github.com/puppetlabs/puppet/pull/7311 should be preferred over https://github.com/puppetlabs/puppet/pull/5814 as it includes the same stripping of Puppet's RUBY_DIR from PATH prior to setting gemcmd on Windows Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Adam Bottchen commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows I have removed it from the CS Top 10. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Thomas Kishel commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Oh, yes. There are other issues with more activity without a workaround. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Fix Version/s: PUP 6.y Fix Version/s: PUP 7.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Scott McClellan updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Scott McClellan Fix Version/s: PUP 5.y Fix Version/s: PUP 6.y Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Story Points: 5 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Labels: cs_pr_review customer gem package provider windows Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Team: Windows Platform OS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols assigned an issue to Unassigned Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Erick Banks commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Geoff Nichols does this work fall under Platform OS team's charter to work on? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Team: Platform OS Windows Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Thomas Kishel updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Thomas Kishel Comment: That PR is rather old, it may need to be rebased. I’m on PTO today. I couldlook at it on Monday. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Thomas Kishel commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows That PR is rather old, it may need to be rebased. I’m on PTO today. I could look at it on Monday. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Thomas Kishel commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows This bug prevents Package Inspection from being able to inspect system gems, making Package Inspection inaccurate. I wrote a module to workaround this bug: https://forge.puppet.com/tkishel/system_gem It's basically the PR. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Owen Rodabaugh CS Priority: Reviewed Minor CS Impact: This can be worked around via an exec. It's another tick against supporting windows as a first class citizen in our ecosystem. CS Severity: 2 - Annoyance CS Business Value: 3 - CS Frequency: 1 - 1-5% of Customers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Maggie Dreyer assigned an issue to Ethan Brown Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Maggie Dreyer Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Moses Mendoza Labels: gem package provider triaged windows Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Chris Denneen commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Same issue with `sensu_gem` provider with the master branch of sensu/sensu on github (this fixed some other issues for Windows installs that haven't been released to forge). Current `package` installs of `sensu-plugins-windows` using `provider => sensu_gem` install the gem's in puppet/sys/ruby/bin instead of sensu/embedded/bin/ Can this be fixed in LTS as well. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Story Points: 5 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Sprint: Agent Needs Information Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Adam Bottchen assigned an issue to Unassigned Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Adam Bottchen Assignee: Adam Bottchen Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Thomas Kishel commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows 1) The specific issue is that Windows users cannot manage Ruby gems because our Ruby is placed first in the PATH on Windows. The most recent PR (earlier ones overreached) addresses this specific issue with a few lines of code. 2) The general issue is that package providers use 'which' to find the first command (for example, 'gem') specified in code by the provider. This 'first' model prevents managing 'multiple.' One suggested solution is for users to create a new provider that inherits from the base provider. Creating a new provider (for example: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/puppet_gem.rb) to specify commands for each instance of a provider seems excessive compared to being able to specify commands via a parameter. Here's a different/similar case (https://tickets.puppetlabs.com/browse/PUP-6895) where the 'first' model fails (albeit due to an unfortunate choice by a Perl developer to name a command 'pip') that could be resolved by being able to specify the full path of the command as a parameter. A command parameter could/would need to be used to establish a third level uniqueness key, as per https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type/package.rb#L274 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols assigned an issue to Adam Bottchen Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Assignee: Adam Bottchen Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title John Duarte updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: John Duarte QA Risk Assessment: Automate Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Acceptance Criteria: - Ability to opt-in to behavior where Puppet's vendored Ruby is not in the PATH. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Fix Version/s: PUP 6.0.0 Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Sprint: Agent Accepted Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Rob Reynolds Labels: gem package provider windows Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Thomas Kishel commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows I've updated the pull request that: reverts puppet_gem.rb, defines a new which_without_puppet_paths method in package.rb that reuses the existing which method, and updates gem.rb to use that new method, which is then also available to other package providers. It's a limited set of changes with a limited scope that restores functionality to the gem provider on Windows, and allows time to consider adding attributes to providers. Implementing attributes to allow multiple-instance packages via an explicit command will require identifying an attribute to maintain uniqueness via a composite uniqueness key. It looks like the command attribute is the best candidate. For example: ['sinatra', 'gem', '/usr/bin/gem']. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title
Thomas Kishel commented on PUP-6134
Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Reviewing our list of package providers, I see two types of providers: single-instance and multiple-instance. For the single-instance providers, such as yum, there
should
be only one executable, and it
should
be in PATH. For multiple-instance providers, such as gem, there could be n-number of instances, each with its own executable and none of them may be in PATH. We recognize this with our puppet_gem provider, which differs from the gem provider only in that it defines an absolute path to :gemcmd (except on Windows).
The provider attribute of a package is, in practice, overloaded as a command attribute: but is an attribute that does not accept an absolute path. An optional command (or to a lesser extent{{environment}} and/or path) attribute for providers, as implemented in the Exec resource type would support multiple-instance providers without requiring a custom provider type for each instance.
So, I agree that an attribute-based solution would be preferable to the PR, which is limited to addressing this issue for one provider on one operating system. Modifying the package type is larger in scope, and may best be executed by someone else, but I'm willing.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Ethan Brown commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows I've made some comments on the new PR at https://github.com/puppetlabs/puppet/pull/5460 We can't modify the existing .bat files or there will be breakage. I'm leaning toward modifying the package type to express a path / command parameter override OR alternatively an environment like exec that allows for complete customization of PATH. Only then would it be easy to install gems in multiple Ruby versions on a system. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Kenaz Kwa updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Kenaz Kwa Team: Agent & Platform Support Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Nate McCurdy updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Nate McCurdy CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title
Nate McCurdy commented on PUP-6134
Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
After a bit of testing, realized that this is not idempotent. The gem gets installed on every puppet run.
package { 'colored':
ensure = present
provider=> 'gem',
install_options => {'--install-dir' => 'C:\tools\ruby22\lib\ruby\gems\2.2.0', '--bindir' => 'c:\tools\ruby22\bin'},
}
The reason for that is because the is state is determined by running C:/Program Files/Puppet Labs/Puppet/sys/ruby/bin/gem.bat list --local ^colored$. So it's searching Puppet's gem list rather than the "system" gem list.
Add Comment
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Kylo Ginsberg commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Are there downsides to modify the .bat files to build a path where puppet's bin directories are at the end of the path? Offhand it does seem preferable to have Windows use the model on *nix where you can simply select the provider, gem vs puppet_gem rather than tinkering with install_options. Also, a note that if we make that change we'll also need to update the puppet_gem provider we added in puppet 4, because it's implementation at https://github.com/puppetlabs/puppet/blob/4.4.1/lib/puppet/provider/package/puppet_gem.rb#L9-L13 currently relies on the path being setup as it is, rather than the provider knowing the path to puppet's ruby's gem (as it does on *nix). Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title
Nate McCurdy commented on PUP-6134
Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Thanks for the clarification Ben Ford. That's exactly my point.
There are many other reasons that someone would want a gem on their Windows system that have nothing to do with developing Puppet modules. Are we going to tell them to use Puppet's Ruby stack for all of those reasons? If the answer is yes, then that is completely opposite of our answer on the *nix side of things.
The gem provider should ideally function exactly the same or at least have feature parity on all Puppet supported operating systems. In its current state, it does the exact opposite of its description when used on Windows. It does what the puppet_gem provider was made for.
A user should be able to run this Puppet code on any supported OS and expect the same outcome. That is the Puppet way after all.
# - minecraftctl to interact with a MineCraft server.
# - gist to be able to share code snippets on gist.github.com.
# - github to be able to interact with GitHub's API.
# - colored to be able to add color to fun little Ruby scripts.
package { [ 'minecraftctl', 'gist', 'github', 'colored' ] :
ensure => present,
provider => gem,
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title
Ben Ford commented on PUP-6134
Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
I think that the choice of gems described may not have been the best. Let's say that the intent was to install minecraftctl so that the logged in user could issue commands to their Minecraft server. On Linux/OSX/whatever, that would be
package { 'minecraftctl':
ensure => present,
provider => gem,
}
and on Windows it would be
package { 'minecraftctl':
ensure => present,
provider => gem,
#some weird arbitrary values that some forum said to use. I dunno what they do.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title
Ethan Brown commented on PUP-6134
Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Typically when customers are performing module development on Windows, there are a couple of options:
Use the Ruby vendored with Puppet and avoid dealing with installing / managing Ruby
Manually install a Ruby version (or multiples) and manage those by hand. This is essentially what the Windows team does to build / test Puppet code – but note this isn't a scenario where I would recommend using Puppet to manage the system. In other words, it's generally recommended against installing both Puppet and various Ruby runtimes if the intent is to do module development.
Furthermore, a local module project should use / manage gems with bundler by specifying dependencies like puppet-lint in a Gemfile specific to the project, and using bundle install --path to segregate the gems - installing a global puppet-lint is not desireable.
So it would be good to get a better sense of:
Why is Puppet being used to manage this scenario?
Is it really for desktop based module dev?
Have you tried specifying install_options to the Puppet package so that installation directories may be specified to gem - http://guides.rubygems.org/command-reference/#gem-install:
package { 'puppet-lint':
ensure => present,
provider => 'gem',
require => Package['ruby'],
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title
Nate McCurdy updated an issue
Puppet / PUP-6134
Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Change By:
Nate McCurdy
Puppet is unable to install a Ruby gem into anything other than Puppet's Ruby stack on Windows nodes.h2. Example of the issueFor example, say I want to install the {{puppet-lint}} gem so that I can validate Puppet code while writing modules. Normally, I'd install Ruby from http://rubyinstaller.org/ then run {{gem install puppet-lint}}. But, let's say I wanted to automate that process using Puppet! First, I would install Chocolatey then use Chocolatey to install Ruby:{code}include chocolateypackage { 'ruby': ensure => present, provider => 'chocolatey', require => Class['chocolatey'],}{code}Then I'd use the gem provider to install puppet-lint:{code}package { 'puppet-lint': ensure => present, provider => 'gem', require => Package['ruby'],}{code} A {{--debug}} log of that package installation looks like this:{code}C:\Users\Administrator>puppet resource package puppet-lint ensure=present provider=gem --debug(... removing Facter resolution messages ...)Debug: /Package[puppet-lint]: Provider gem does not support features virtual_packages; not managing attribute allow_virtualDebug: Loaded state in 0.03 secondsDebug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Failed to load library 'selinux' for feature 'selinux'Debug: Prefetching gem resources for packageDebug: Executing: 'C:/Program Files/Puppet Labs/Puppet/sys/ruby/bin/gem.bat list --local'Debug: Finishing transaction 39019400Debug: Storing stateDebug: Stored state in 0.05 secondspackage { 'puppet-lint': ensure => ['1.1.0'],}{code} After doing this, the {{puppet-lint}} executable is not available in %PATH%, and {{gem list}} doesn't show puppet-lint as installed:{code}C:\Users\Administrator>puppet-lint'puppet-lint' is not recognized as an internal or external command,operable program or batch file.C:\Users\Administrator>gem list*** LOCAL GEMS ***bigdecimal (1.2.6)io-console (0.4.3)json (1.8.1)minitest (5.4.3)power_assert (0.2.2)psych (2.0.8)rake (10.4.2)rdoc (4.2.0)test-unit (3.0.8)C:\Users\Administrator>{code}*But*, if I use's Puppet's {{gem}} command, I see that puppet-lint got installed into Puppet's Ruby stack:{code}C:\Users\Administrator>"C:\Program Files\Puppet Labs\Puppet\sys\ruby\bin\gem.bat" list*** LOCAL GEMS ***bigdecimal (1.2.4)deep_merge (1.0.1)ffi (1.9.10 x64-mingw32)io-console (0.4.3, 0.4.2)json (1.8.1)minitar (0.5.4)minitest (4.7.5)psych (2.0.5)puppet-lint (1.1.0)rake (10.1.0)rdoc (4.1.0)stomp (1.3.3)test-unit (2.1.8.0, 2.1.7.0, 2.1.6.0, 2.1.5.0)win32-dir (0.4.9)win32-eventlog (0.6.2)win32-process (0.7.4)win32-security (0.2.5)win32-service (0.8.6){code}h2. Likely CausePuppet is putting its bin directory at the start of %PATH% during all invocations of {{puppet}}, which causes the {{gem}} provider to find
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Henrik Lindberg Scrum Team: Windows Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Nate McCurdy created an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Issue Type: Bug Affects Versions: PUP 4.3.2 Assignee: Unassigned Components: Windows Created: 2016/04/06 4:45 PM Priority: Normal Reporter: Nate McCurdy Puppet is unable to install a Ruby gem into anything other than Puppet's Ruby stack on Windows nodes. Example of the issue For example, say I want to install the puppet-lint gem so that I can validate Puppet code while writing modules. Normally, I'd install Ruby from http://rubyinstaller.org/ then run gem install puppet-lint. But, let's say I wanted to automate that process using Puppet! First, I would install Chocolatey then use Chocolatey to install Ruby: include chocolatey
