grnhse / greenhouse_io

Ruby API wrapper for Greenhouse.io API
MIT License
44 stars 46 forks source link

bundle install issue in ruby 3 #47

Closed atrzaska closed 3 years ago

atrzaska commented 3 years ago

currently my bundle won't install because of this issue

Installing mimemagic 0.4.3 with native extensions
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

    current directory: /Users/andrzej/Documents/honeypot/honeypot/vendor/bundle/ruby/3.0.0/gems/mimemagic-0.4.3/ext/mimemagic
/usr/local/opt/ruby/bin/ruby -I/usr/local/Cellar/ruby/3.0.1/lib/ruby/3.0.0 -rrubygems
/Users/andrzej/Documents/honeypot/honeypot/vendor/bundle/ruby/3.0.0/gems/rake-12.3.3/exe/rake
RUBYARCHDIR\=/Users/andrzej/Documents/honeypot/honeypot/vendor/bundle/ruby/3.0.0/extensions/x86_64-darwin-20/3.0.0/mimemagic-0.4.3
RUBYLIBDIR\=/Users/andrzej/Documents/honeypot/honeypot/vendor/bundle/ruby/3.0.0/extensions/x86_64-darwin-20/3.0.0/mimemagic-0.4.3
rake aborted!
ArgumentError: wrong number of arguments (given 2, expected 1)
/Users/andrzej/Documents/honeypot/honeypot/vendor/bundle/ruby/3.0.0/gems/mimemagic-0.4.3/ext/mimemagic/Rakefile:28:in `block in <top (required)>'
/Users/andrzej/Documents/honeypot/honeypot/vendor/bundle/ruby/3.0.0/gems/rake-12.3.3/exe/rake:27:in `<main>'
Tasks: TOP => default
(See full trace by running task with --trace)

rake failed, exit code 1

Gem files will remain installed in /Users/andrzej/Documents/honeypot/honeypot/vendor/bundle/ruby/3.0.0/gems/mimemagic-0.4.3 for inspection.
Results logged to /Users/andrzej/Documents/honeypot/honeypot/vendor/bundle/ruby/3.0.0/extensions/x86_64-darwin-20/3.0.0/mimemagic-0.4.3/gem_make.out

An error occurred while installing mimemagic (0.4.3), and Bundler cannot continue.
Make sure that `gem install mimemagic -v '0.4.3' --source 'https://rubygems.org/'` succeeds before bundling.

In Gemfile:
  greenhouse_io was resolved to 2.5.0, which depends on
    httmultiparty was resolved to 0.3.16, which depends on
      mimemagic

seems like httpmultiparty is not maintained.

atrzaska commented 3 years ago

The issue happened with rake 12.3.3

updating it fixed the issue.

Fetching rake 13.0.6 (was 12.3.3)
Installing rake 13.0.6 (was 12.3.3)