Issue #17835 has been updated by Justin Honold.
It isn't a barrier. The use-case was a server upon which a developer wanted both 1.9.3 MRI and JRuby gems to be installed. I asked if using just JRuby (necessary) could be sufficient, he said yes, so I endeavored to install Puppet in that. Which would have made it a lot cleaner, because I could do gem installs using the Puppet package provider. As it stands, I have it split: 1.9.3 w/gems, then a script which calls out to JRuby to ensure those gems are in place. I'm going to Tweet a (the?) prominent JRuby dev, to see if he has any input about Puppet/fork/OpenSSL. ---------------------------------------- Bug #17835: JRuby appears to fail out because the RPM provider needs fork support https://projects.puppetlabs.com/issues/17835#change-77703 Author: Justin Honold Status: Closed Priority: Normal Assignee: eric sorenson Category: Target version: Affected Puppet version: Keywords: Branch: https://github.com/puppetlabs/puppet-docs/pull/118 * jruby 1.7.0 (1.9.3p203) 2012-10-22 ff1ebbe on Java HotSpot(TM) 64-Bit Server VM 1.7.0_09-b05 [linux-amd64] * facter (1.6.14) * hiera (1.0.0) * puppet (3.0.1) <pre> /usr/local/rvm/gems/jruby-1.7.0/gems/puppet-3.0.1/lib/puppet/status.rb:8 warning: optional boolean argument is obsoleted The signal USR1 is in use by the JVM and will not work correctly on this platform Info: Retrieving plugin Error: Could not autoload puppet/provider/package/rpm: fork is not available on this platform Error: Could not autoload puppet/provider/package/zypper: Could not autoload puppet/provider/package/rpm: fork is not available on this platform Error: Could not autoload puppet/type/package: Could not autoload puppet/provider/package/zypper: Could not autoload puppet/provider/package/rpm: fork is not available on this platform Error: Could not retrieve catalog from remote server: Could not intern from pson: Could not autoload puppet/type/package: Could not autoload puppet/provider/package/zypper: Could not autoload puppet/provider/package/rpm: fork is not available on this platform Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run Error: Could not save last run local report: can't convert Pathname into String Error: Could not save yaml my.hostname.com: can't convert Pathname into String </pre> Is this still a supported platform a la http://puppetlabs.com/blog/puppet-2-6-1-released/ ? MRI 1.8.7 and 1.9.3 both work fine. -- 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.
