Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deps have changed, resulting in install failure #28

Closed
jkugler opened this issue Jul 23, 2019 · 6 comments
Closed

Deps have changed, resulting in install failure #28

jkugler opened this issue Jul 23, 2019 · 6 comments

Comments

@jkugler
Copy link

jkugler commented Jul 23, 2019

Version 2.1.0 (latest)
CentOS 7 (latest updates)
Tried with Redmine 3.4.6 and 3.4.11

It would appear something in the dependency tree was updated, and versions were not properly pinned. That is odd, because the error is:

An error occurred while installing rmagick (4.0.0), and Bundler cannot continue.

but the Gemfile for Redmine says:

	
# Optional gem for exporting the gantt to a PNG file, not supported with jruby
group :rmagick do
  gem "rmagick", "~> 2.16.0"
end

TASK [bngsudheer.redmine : Install the gems needed by Redmine via bundler]
results in:

FAILED! => {"changed": false, "cmd": "/home/redmine/bin/bundler install --gemfile /srv/redmine/redmine/Gemfile", "msg": "/usr/share/gems/gems/psych-2.0.0/lib/psych.rb:98: warning: already initialized constant Psych::VERSION
/usr/share/ruby/psych.rb:98: warning: previous definition of VERSION was here
/usr/share/gems/gems/psych-2.0.0/lib/psych.rb:101: warning: already initialized constant Psych::LIBYAML_VERSION
/usr/share/ruby/psych.rb:101: warning: previous definition of LIBYAML_VERSION was here", "rc": 5, "stderr": "/usr/share/gems/gems/psych-2.0.0/lib/psych.rb:98: warning: already initialized constant Psych::VERSION
/usr/share/ruby/psych.rb:98: warning: previous definition of VERSION was here
/usr/share/gems/gems/psych-2.0.0/lib/psych.rb:101: warning: already initialized constant Psych::LIBYAML_VERSION
/usr/share/ruby/psych.rb:101: warning: previous definition of LIBYAML_VERSION was here
", "stderr_lines": ["/usr/share/gems/gems/psych-2.0.0/lib/psych.rb:98: warning: already initialized constant Psych::VERSION", "/usr/share/ruby/psych.rb:98: warning: previous definition of VERSION was here", "/usr/share/gems/gems/psych-2.0.0/lib/psych.rb:101: warning: already initialized constant Psych::LIBYAML_VERSION", "/usr/share/ruby/psych.rb:101: warning: previous definition of LIBYAML_VERSION was here"], "stdout": "The dependency tzinfo-data (>= 0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby but the dependency is only for x86-mingw32, x64-mingw32, x86-mswin32. To add those platforms to the bundle, run `bundle lock --add-platform x86-mingw32 x64-mingw32 x86-mswin32`.
Fetching gem metadata from https://rubygems.org/................
Fetching gem metadata from https://rubygems.org/..
Resolving dependencies....
RubyGems 2.0.14.1 is not threadsafe, so your gems will be installed one at a time. Upgrade to RubyGems 2.1.0 or higher to enable parallel gem installation.
Using rake 12.3.3
Using i18n 0.7.0
Using minitest 5.11.3
Using thread_safe 0.3.6
Using tzinfo 1.2.5
Using activesupport 4.2.8
Using builder 3.2.3
Using erubis 2.7.0
Using mini_portile2 2.1.0
Using nokogiri 1.6.8.1
Using rails-deprecated_sanitizer 1.0.3
Using rails-dom-testing 1.0.9
Using crass 1.0.4
Using loofah 2.2.3
Using rails-html-sanitizer 1.0.4
Using actionview 4.2.8
Using rack 1.6.11
Using rack-test 0.6.3
Using actionpack 4.2.8
Using globalid 0.4.2
Using activejob 4.2.8
Using mime-types-data 3.2019.0331
Using mime-types 3.2.2
Using mail 2.6.6
Using actionmailer 4.2.8
Using actionpack-xml_parser 1.0.2
Using activemodel 4.2.8
Using arel 6.0.4
Using activerecord 4.2.8
Using public_suffix 2.0.5
Using addressable 2.6.0
Using bundler 1.16.1
Using mini_mime 1.0.2
Using xpath 2.1.0
Using capybara 2.18.0
Using ffi 1.11.1
Using childprocess 0.9.0
Using coderay 1.1.2
Using concurrent-ruby 1.1.5
Using css_parser 1.7.0
Using docile 1.1.5
Using htmlentities 4.3.4
Using thor 0.20.3
Using railties 4.2.8
Using jquery-rails 3.1.5
Using kgio 2.11.2
Using metaclass 0.0.4
Using mimemagic 0.3.3
Using mocha 1.9.0
Using multi_json 1.13.1
Using net-ldap 0.12.1
Using pg 0.18.4
Using protected_attributes 1.1.4
Using ruby-openid 2.3.0
Using rack-openid 1.4.2
Using sprockets 3.7.2
Using sprockets-rails 3.2.1
Using rails 4.2.8
Using raindrops 0.19.0
Using rbpdf-font 1.19.1
Using rbpdf 1.19.8
Using rdoc 4.3.0
Using redcarpet 3.4.0
Using request_store 1.0.5
Fetching rmagick 4.0.0
Installing rmagick 4.0.0 with native extensions
Gem::InstallError: rmagick requires Ruby version >= 2.3.0.
An error occurred while installing rmagick (4.0.0), and Bundler cannot continue.
Make sure that `gem install rmagick -v '4.0.0'` succeeds before bundling.

In Gemfile:
  rmagick
", "stdout_lines": ["The dependency tzinfo-data (>= 0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby but the dependency is only for x86-mingw32, x64-mingw32, x86-mswin32. To add those platforms to the bundle, run `bundle lock --add-platform x86-mingw32 x64-mingw32 x86-mswin32`.", "Fetching gem metadata from https://rubygems.org/................", "Fetching gem metadata from https://rubygems.org/..", "Resolving dependencies....", "RubyGems 2.0.14.1 is not threadsafe, so your gems will be installed one at a time. Upgrade to RubyGems 2.1.0 or higher to enable parallel gem installation.", "Using rake 12.3.3", "Using i18n 0.7.0", "Using minitest 5.11.3", "Using thread_safe 0.3.6", "Using tzinfo 1.2.5", "Using activesupport 4.2.8", "Using builder 3.2.3", "Using erubis 2.7.0", "Using mini_portile2 2.1.0", "Using nokogiri 1.6.8.1", "Using rails-deprecated_sanitizer 1.0.3", "Using rails-dom-testing 1.0.9", "Using crass 1.0.4", "Using loofah 2.2.3", "Using rails-html-sanitizer 1.0.4", "Using actionview 4.2.8", "Using rack 1.6.11", "Using rack-test 0.6.3", "Using actionpack 4.2.8", "Using globalid 0.4.2", "Using activejob 4.2.8", "Using mime-types-data 3.2019.0331", "Using mime-types 3.2.2", "Using mail 2.6.6", "Using actionmailer 4.2.8", "Using actionpack-xml_parser 1.0.2", "Using activemodel 4.2.8", "Using arel 6.0.4", "Using activerecord 4.2.8", "Using public_suffix 2.0.5", "Using addressable 2.6.0", "Using bundler 1.16.1", "Using mini_mime 1.0.2", "Using xpath 2.1.0", "Using capybara 2.18.0", "Using ffi 1.11.1", "Using childprocess 0.9.0", "Using coderay 1.1.2", "Using concurrent-ruby 1.1.5", "Using css_parser 1.7.0", "Using docile 1.1.5", "Using htmlentities 4.3.4", "Using thor 0.20.3", "Using railties 4.2.8", "Using jquery-rails 3.1.5", "Using kgio 2.11.2", "Using metaclass 0.0.4", "Using mimemagic 0.3.3", "Using mocha 1.9.0", "Using multi_json 1.13.1", "Using net-ldap 0.12.1", "Using pg 0.18.4", "Using protected_attributes 1.1.4", "Using ruby-openid 2.3.0", "Using rack-openid 1.4.2", "Using sprockets 3.7.2", "Using sprockets-rails 3.2.1", "Using rails 4.2.8", "Using raindrops 0.19.0", "Using rbpdf-font 1.19.1", "Using rbpdf 1.19.8", "Using rdoc 4.3.0", "Using redcarpet 3.4.0", "Using request_store 1.0.5", "Fetching rmagick 4.0.0", "Installing rmagick 4.0.0 with native extensions", "Gem::InstallError: rmagick requires Ruby version >= 2.3.0.", "An error occurred while installing rmagick (4.0.0), and Bundler cannot continue.", "Make sure that `gem install rmagick -v '4.0.0'` succeeds before bundling.", "", "In Gemfile:", "  rmagick"]}
@jkugler
Copy link
Author

jkugler commented Jul 23, 2019

Seems 3.4.x actually has this in the Gemfile:

  # Optional gem for exporting the gantt to a PNG file, not supported with jruby
  group :rmagick do
    gem "rmagick", ">= 2.14.0"
  end

which would explain why it's trying to pull in 4.0.0

@jkugler
Copy link
Author

jkugler commented Jul 23, 2019

Something odd going on. https://www.redmine.org/projects/redmine/repository/entry/tags/3.4.11/Gemfile says:

  # Optional gem for exporting the gantt to a PNG file, not supported with jruby
  group :rmagick do
    gem "rmagick", "~> 2.16.0"
  end

but my on-disk copy had >=. Will continue to investigate.

@jkugler
Copy link
Author

jkugler commented Jul 23, 2019

Looks like between .6 and .11 they corrected it to ~>. I'll blow away my machine and start fresh with 3.4.11

@jkugler
Copy link
Author

jkugler commented Jul 23, 2019

That seemed to fix that bug. Hit a "DB doesn't exist" issue, but pretty sure that is my fault. Will continue debugging tomorrow.

@jkugler
Copy link
Author

jkugler commented Jul 24, 2019

Yes, the error seems to have been fixed in a later redmine version. Default to 3.4.11 will fix the error on CentOS/Redhat 7.

@bngsudheer
Copy link
Owner

Thanks for tracing the issue. I have bumped the default version. Waiting for CI results :)

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

No branches or pull requests

2 participants