jruby/cucumber: Bundle install doesn't install any gem - cucumber

I'm on Windows 10 x64 and I've installed JRuby 1.7.8 (I tried the files for x64 and 32bits with the same problem) and JRE 7.
I was trying to have my Cucumber Test Framework running on a different machine. I downloaded my current branch (which is working fine in other computers, with all the settings: env.rb, Gemfile, etc) and then I installed successfully these 2 gems:
gem install bundler
gem install cucumber
The Gemfile I have contains loads of gems, similar to:
source 'https://rubygems.org'
gem "httpclient"
gem "watir-webdriver"
but when I execute:
bundle install
I just get this line and nothing gets installed, it finishes almost immediately. No Gemfile.lock is created, etc.
D:\project>bundle install
io/console not supported; tty will not be manipulated
D:\project>
Any idea what could be wrong and what I could try please?
Not quite sure if the issue has anything to do with the line above (which I had never seen in the other machines that are working). If it's not related and you've got an idea about both problems, please let me know and I'll have a look as well...
I've been trying for a few more hours and still not success, adding further info in case someone can spot something pls. Even 'bundle -v' doesn't work on this machine?!
D:\project>gem list
io/console not supported; tty will not be manipulated
*** LOCAL GEMS ***
builder (3.2.2)
bundler (1.13.2)
cucumber (2.4.0)
cucumber-core (1.5.0)
cucumber-wire (0.0.1)
diff-lcs (1.2.5)
gherkin (4.0.0)
jruby-win32ole (0.8.5)
multi_json (1.12.1)
multi_test (0.1.2)
rake (10.1.0)
D:\project>bundle -v
io/console not supported; tty will not be manipulated
D:\project>
Cheers!!

You have the latest version of bundler 1.13.2 installed and I have seen it cause different types of issues depending on the jruby version and some other gems. Bundler 1.10.6 works everytime for my Jruby 1.7.x.
Try these:
gem uninstall bundler
and
gem install bundler -v 1.10.6

Although I am not particularly familiar with jruby, it appears to be a bug, which is resolved in JRuby 1.7.24.
I would verify that the other computers this is working on are still on that version of jruby (assuming they are windows boxes).

Related

Which packages should I install on Cygwin to use simpleScalar - Alpha configuration?

I already installed the following packages version 4.3-1, gcc-core version 11.3.0-1, gcc-g++ version 11.3.0-1. However, when I run the make command after running the make config-alpha command, I get several errors on the screen. I already tried to install other versions of these packages but I still get the same results.errors that I got
Which other additional package should I install?
Assuming that SimpleScalar is the one here:
https://www.es.ele.tue.nl/~yhe/aca/Simplescalar_Download.html
the packaging is ancient (gcc gcc-2.7.2.3) and its manually crafted configure is not considering any recent platforms.
It seems very hard to adjust to a Cygwin build and you can not use the GCC Cygwin compiler for a cross build of a Alpha platform

I just installed Nodejs 14.4 from the site, but when I check the version in Command Prompt it shows version 8.10

title says it all. I have been using nodejs with npm for while now and it has been working fine, but I went to check the version and noticed it was an older one. Nodejs - version 8.10.0 and npm - version 3.5.2. I know there are more recent versions of each and like I said I went to download the new version of Nodejs and I got it. I have the path set up to its location in my Environment Variable. I'm not sure what I'm missing. Would love any help.
Edit: Forgot to mention on my original post that I am on Windows.
Edit2: So I was looking at it more and I am using the Ubuntu Bash Shell on muy windows computer. Whenever I check the version in the normal Windows Command Prompt it displays the right version, but when I check it in the Bash shell it is wrong. Any ideas why this happens?
The Node Version Manager. You can find it at https://github.com/coreybutler/nvm-windows
It allows you to easily install and manage multiple versions of node. Here's a snippet from the help:
Usage:
nvm install <version> Download and install a <version>
nvm use <version> Modify PATH to use <version>
nvm ls List versions (installed versions)
install and Usage:
nvm install 6.14.4 # or 10.10.0, 8.9.1, etc
and then
nvm use 6.14.4
So, I was able to solve my own issue
These two links were very important for solving my issue:
E: Unable to locate package npm
https://learn.microsoft.com/en-us/windows/wsl/install-win10#update-to-wsl-2
So basically after uninstalling nodejs I went and tried uninstalling and reinstalling my Ubuntu Bash shell. Once I had the Bash shell set up again I tried running the commands listed in the stackoverflow post I have listed above. (note: When you run the curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash - line you need to adjust the "setup" version to 14.x) When I ran all the commands I was able to get my npm version up-to-date, but my nodejs was still being stuck at version 10.x. I tried running the install again on nodejs and thats when I noticed an error reading gpg: can't connect to the agent: IPC connect call failed I did some research on this error and foudn out my WSL1 would not allow it to update to the most recent version. Thats how I found my way to the Microsoft page that led to me needing to update my version of Windows to 1909 and then installing WSL2 through Power Shell. Everything is now up-to-date and working!
You could Uninstall both versions and reinstall the newer version. That should do it
Or better still download the NVM and follow the instructions from here
https://blog.logrocket.com/switching-between-node-versions-during-development/

Puma gem does not build with Pakyow new blog

I am trying to get Pakyow project built, but the build stops at (gem) Puma error. I am curious how Pakyow got beyond this Puma error? Basically the gem install puma does not build/bundle.
Installing Puma on Windows
I found these steps at https://github.com/hicknhack-software/rails-disco/wiki/Installing-puma-on-windows. From there, you can find links to libraries and programs.
Install DevKit for your Ruby version, e.g. in c:\devkit
Download and unpack the OpenSSL Package, e.g. in c:\openssl (use 7Zip or PeaZip)
Copy the DLLs from the bin directory (libeay32.dll and ssleay32.dll) to your ruby/bin directory.
Open a Windows console/command prompt
Initialize the DevKit build environment by changing directory to the directory you installed DevKit cd \devkit and running the batch file devkitvars.bat
Install the puma gem with the OpenSSL packages gem install puma -- --with-opt-dir=c:\openssl
Verify in command prompt with puma -v
skylenewman's suggestion worked for my. I have a Windows 7 32-bit OS.
I also tried this on a Win7 64-bit and was hitting errors on puma gem installation. I'm not sure if it's a directory structure issue as I put the /devkit and /openssl on the F: drive instead of C:.

Vagrant Installation in Debian Os

I have been trying to install and set up vagrant in my local machine which runs on debian OS for PHP project.
As mentioned in the link https://www.virtualbox.org/wiki/Linux_Downloads, I followed all the setups listed for installing Virtual Box initially. After successful installation I tried installing Vagrant by downloading it from official website. Once all installation is done, I create a directory called website cd into it and gave the command
Vagrant init
For vagrant initialization. But vagrant returns me the following error. How to resolve this?
Vagrant experienced a version conflict with some installed plugins!
This usually happens if you recently upgraded Vagrant. As part of the
upgrade process, some existing plugins are no longer compatible with
this version of Vagrant. The recommended way to fix this is to remove
your existing plugins and reinstall them one-by-one. To remove all
plugins:
rm -r ~/.vagrant.d/plugins.json ~/.vagrant.d/gems
Note if you have an alternate VAGRANT_HOME environmental variable
set, the folders above will be in that directory rather than your
user's home directory.
The error message is shown below:
Bundler could not find compatible versions for gem "rest-client":
In Gemfile:
vagrant (= 1.7.0) ruby depends on
rest-client (~> 1.7) ruby
vagrant-share (>= 0) ruby depends on
rest-client (1.6.8)

"spawn.h not found" while installing octopress on Cygwin

I have been trying to install octopress on cygwin. I have googled but no avail. I hope that someone can suggest a hack (no matter how complicated) to resolve this.
I followed the octopress installation instructions. Everything went smoothly till the bundle install stage. When I reached that point, the installation quits with the error telling that it couldn't find spawn.h.
I searched and apparently spawn.h doesn't come in any of the cygwin libraries. I installed all the c++ libraries I could from cygwin setup but that did not help.
Can you please help resolve this?
I think the gem that fails in this process is posix-spawn. For this, you could install the gem locally:
$ gem install rake-compiler -v 0.7.6
$ git clone git://github.com/rtomayko/posix-spawn.git
$ cd posix-spawn
$ rake gem
$ cd pkg/posix-spawn-0.3.6
$ gem install --local posix-spawn-0.3.6.gem
The explanation (from an article I found):
There is a bug in the version of posix-spawn in the gem repositories however that makes installing via gem impossible on Cygwin
After this, try bundle install again, it should be successful.
Here's a related issue on the GitHub project
UPDATE: I recently installed scoop a command-line installer for Windows, a pretty easy setup. I installed Ruby, bundler and octopress without breaking a sweat. You should give it a try.

Resources