I just installed the pushy client on a windows 2008r2 server with chef
12.0.3 already installed and noticed it completely hijacks chef’s own GEM
path causing all attempts to load other gems to fail.
------ gem env ------
RubyGems Environment:
- RUBYGEMS VERSION: 1.8.28
- RUBY VERSION: 1.9.3 (2013-11-22 patchlevel 484) [i386-mingw32]
- INSTALLATION DIRECTORY: C:/opscode/pushy/embedded/lib/ruby/gems/1.9.1
- RUBY EXECUTABLE: C:/opscode/pushy/embedded/bin/ruby.exe
- EXECUTABLE DIRECTORY: C:/opscode/pushy/embedded/bin
- RUBYGEMS PLATFORMS:
- GEM PATHS:
- C:/opscode/pushy/embedded/lib/ruby/gems/1.9.1
- C:/Users/Administrator/.gem/ruby/1.9.1
- GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :benchmark => false
- :backtrace => false
- :bulk_threshold => 1000
- REMOTE SOURCES:
The install was used via the push-jobs cookbook.
Anyone else notice this?
–
Thanks,
Mark
Last I had checked pushy wasn't available for Windows; nice to see they're
closing that gap. Maybe x86 and not insisting on runit under Linux will
come down the pipe as well...
On Feb 13, 2015 8:20 AM, "Mark Pimentel" markpimentel22@gmail.com wrote:
I just installed the pushy client on a windows 2008r2 server with chef
12.0.3 already installed and noticed it completely hijacks chef's own GEM
path causing all attempts to load other gems to fail.
------ gem env ------
RubyGems Environment:
- RUBYGEMS VERSION: 1.8.28
- RUBY VERSION: 1.9.3 (2013-11-22 patchlevel 484) [i386-mingw32]
- INSTALLATION DIRECTORY: C:/opscode/pushy/embedded/lib/ruby/gems/1.9.1
- RUBY EXECUTABLE: C:/opscode/pushy/embedded/bin/ruby.exe
- EXECUTABLE DIRECTORY: C:/opscode/pushy/embedded/bin
- RUBYGEMS PLATFORMS:
- GEM PATHS:
- C:/opscode/pushy/embedded/lib/ruby/gems/1.9.1
- C:/Users/Administrator/.gem/ruby/1.9.1
- GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :benchmark => false
- :backtrace => false
- :bulk_threshold => 1000
- REMOTE SOURCES:
The install was used via the push-jobs cookbook.
Anyone else notice this?
--
Thanks,
Mark