I think checked to see if the “gem” command had the right versions on each server and that is where I located the issue.
The benefits of manually building a copy of Ruby in variable determines where your system searches for command-line programs.
You’ll need to set it so that it can find the new apps you’re about to install.
Earlier when attempting to install the request-log-analyzer gem on a Cent OS Linux server I ran into some issues.
I noticed that on one server I was able to install the request-log-analyzer gem without issue but on another server running the same version of Cent OS and Ruby as the first server the attempt to install request-log-analyzer returned an error.
here too If you don't have any Ruby Gems install, there is still the pre-gem approach to getting software, doing it manually: 1. New features: * `gem` commands * `gem install` and `gem fetch` now report alternate platforms when a matching one couldn't be found.
* `gem contents` --prefix is now the default as specified in --help. I have done the "gem update --system" command, and successfully updated to Ruby Gems 1.3.6.The problem is, Netbeans is not recognizing that I have updated it, even after restarting Netbeans. If you have no network connection or are behind a very restrictive firewall you may find it difficult to install gems.Here is how you work around this problem, provided you have an alternate way of moving the files.Using the editor of your choice, create and edit a file in your home directory named at the beginning of the line returned by the system.