Skip to content
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.

nokogiri installing is ignored (on windows ruby 2.0.0-p0 64bit) #2356

Closed
tetradice opened this issue Mar 2, 2013 · 13 comments
Closed

nokogiri installing is ignored (on windows ruby 2.0.0-p0 64bit) #2356

tetradice opened this issue Mar 2, 2013 · 13 comments

Comments

@tetradice
Copy link

Hi, thank you for release of bundler 1.3.0.

I have found strange work. I installed ruby 2.0.0-p0 (x64) and DevKit mingw64-64 from RubyInstaller 7-zip archive to Windows 8 64bit. Next, I installed bundler 1.3.0 and try to bundle install for nokogiri. So nokogiri is ignored and not installed.

I have expected that nokogiri installing will succeed or simply failed with error messages. But, there was no error message on bundle install. So when I use x86 (32-bit) ruby, nokogiri installing succeeded.

Is its work is expected? If it is not expected, I wish that it is fixed.

Gemfile

source "http://rubygems.org"

gem 'nokogiri'
gem 'hpricot'

Output (on x64 ruby)

$ ruby -v
ruby 2.0.0p0 (2013-02-24) [x64-mingw32]
$ bundle install --path vendor/bundle
Fetching gem metadata from http://rubygems.org/.........
Fetching gem metadata from http://rubygems.org/..
Resolving dependencies...
Installing hpricot (0.8.6)
Using bundler (1.3.0)
Your bundle is complete! It was installed into ./vendor/bundle
$

Output (on x86 ruby)

$ ruby -v
ruby 2.0.0p0 (2013-02-24) [i386-mingw32]
$ bundle install --path vendor/bundle
Fetching gem metadata from http://rubygems.org/.........
Fetching gem metadata from http://rubygems.org/..
Resolving dependencies...
Installing hpricot (0.8.6)
Installing nokogiri (1.5.6)
Using bundler (1.3.0)
Your bundle is complete! It was installed into ./vendor/bundle

Environment

  • Windows 8 64bit
@indirect
Copy link
Member

indirect commented Mar 2, 2013

It seems like there is no nokogiri gem for x64-mingw32: http://rubygems.org/gems/nokogiri/versions. I believe Bundler should say there is an error, and no gem can be found. Do you agree?

@tetradice
Copy link
Author

Thank you for your reply. But, I has repeated 2-3 times after clean files except Gemfile, also error message is nothing.

Addition to it, following Gemfile makes a error message.

source "http://rubygems.org"

gem 'nokogiri'
gem 'hpricot'
gem 'unknowngem20130302'

$ bundle install --path vendor/bundle
Fetching gem metadata from http://rubygems.org/.........
Fetching gem metadata from http://rubygems.org/..
Could not find gem 'unknowngem20130302 (>= 0) x86-mingw32' in the gems available on this machine.
$

@indirect
Copy link
Member

indirect commented Mar 2, 2013

Yes, it does not give an error message. I am sorry. :( I believe this is a bug, and the fix would be to raise an error. Does that seem right to you?

@tetradice
Copy link
Author

Don't be. :-)

I believe this is a bug, and the fix would be to raise an error. Does that seem right to you?

Yes, I think that its behavior is right, too.

@tetradice
Copy link
Author

P.S.
I just noticed after writing my previous message. I must apologize to you.

It seems like there is no nokogiri gem for x64-mingw32: http://rubygems.org/gems/nokogiri/versions. I believe Bundler should say there is an error, and no gem can be found. Do you agree?

I understood as that you disagree that it is bug. But, it is my misreading and I should answer "Yes, I do."

I'm sorry, André. :-<

@indirect
Copy link
Member

indirect commented Mar 3, 2013

No problem! I will try to figure out why there is no error soon. :)

@contentfree
Copy link

@indirect Any idea on this? The strange thing is deleting Gemfile.lock and doing a bundle install again (on an x64 system) generates a Gemfile.lock that says x86-mingw32 under PLATFORMS (instead of x64-mingw32 as ruby -v and gem env report).

@indirect
Copy link
Member

As noted above, there is no nokogiri gem for x64-mingw32. I believe Bundler is trying to use the x86 gem because there isn't one for your actual platform, but I'm pretty sure that's a bug.

On Apr 23, 2013, at 9:43 PM, Dave Myron [email protected] wrote:

@indirect Any idea on this? The strange thing is deleting Gemfile.lock and doing a bundle install again (on an x64 system) generates a Gemfile.lock that says x86-mingw32 under PLATFORMS (instead of x64-mingw32 as ruby -v and gem env report).


Reply to this email directly or view it on GitHub.

@contentfree
Copy link

Right. It is strange that bundle env reports a different platform than gem env. And bundler should probably throw an error (or better yet, let me force it to use the 32-bit version, or both) 👍

@mdesantis
Copy link

I have a similar problem too, on Windows 7 x64 and Ruby 2.0.0-p195-x64 (RubyInstaller); the Gemfile includes

gem 'win32-dir', platforms: :mingw

But Bundler ignores this line; and bundle env reports a different platform than gem env (respectively x86-mingw32 and x64-mingw32)

@mdesantis
Copy link

I tried to find where Bundler performs the platform checking, but I had no success. Does anyone know it?

@mindplay-dk
Copy link

According to the maintainer of the pg gem this issue also currently blocks the installation of pg on Windows.

larskanis added a commit to larskanis/bundler that referenced this issue Aug 10, 2013
@xaviershay
Copy link
Contributor

PR merged!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants