fileutils conflict in Ruby 2.5.1

[Sega100500]

Debian Linux 8.10 Jessie
ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux]
rubygems-update (2.7.7)

Error log:

pp 8789 output: /home/ruby/.rbenv/versions/2.5.1/lib/ruby/2.5.0/fileutils.rb:90: warning: already initialized constant FileUtils::VERSION
App 8789 output: /home/ruby/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fileutils-1.1.0/lib/fileutils.rb:92: warning: previous definition
 of VERSION was here
App 8789 output: /home/ruby/.rbenv/versions/2.5.1/lib/ruby/2.5.0/fileutils.rb:1188: warning: already initialized constant FileUtils::Entry_:
:S_IF_DOOR
App 8789 output: /home/ruby/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fileutils-1.1.0/lib/fileutils.rb:1267: warning: previous definiti
on of S_IF_DOOR was here
App 8789 output: /home/ruby/.rbenv/versions/2.5.1/lib/ruby/2.5.0/fileutils.rb:1446: warning: already initialized constant FileUtils::Entry_:
:DIRECTORY_TERM
App 8789 output: /home/ruby/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fileutils-1.1.0/lib/fileutils.rb:1541: warning: previous definiti
on of DIRECTORY_TERM was here
App 8789 output: /home/ruby/.rbenv/versions/2.5.1/lib/ruby/2.5.0/fileutils.rb:1448: warning: already initialized constant FileUtils::Entry_:
:SYSCASE
App 8789 output: /home/ruby/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fileutils-1.1.0/lib/fileutils.rb:1543: warning: previous definiti
on of SYSCASE was here
App 8789 output: /home/ruby/.rbenv/versions/2.5.1/lib/ruby/2.5.0/fileutils.rb:1501: warning: already initialized constant FileUtils::OPT_TAB
LE
App 8789 output: /home/ruby/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fileutils-1.1.0/lib/fileutils.rb:1596: warning: previous definiti
on of OPT_TABLE was here
App 8789 output: /home/ruby/.rbenv/versions/2.5.1/lib/ruby/2.5.0/fileutils.rb:1555: warning: already initialized constant FileUtils::LOW_MET
HODS
App 8789 output: /home/ruby/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fileutils-1.1.0/lib/fileutils.rb:1650: warning: previous definiti
on of LOW_METHODS was here
App 8789 output: /home/ruby/.rbenv/versions/2.5.1/lib/ruby/2.5.0/fileutils.rb:1562: warning: already initialized constant FileUtils::METHODS
App 8789 output: /home/ruby/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fileutils-1.1.0/lib/fileutils.rb:1657: warning: previous definiti
on of METHODS was here

[hsbt]

This is warnings, not error.

But I understood this issue is harmful. I try to resolve this.

[mcmillion]

I think this is causing some errors. I can't prove it, but after updating system gems today I got this error, and now about half of my previously working rake tasks hang and can't be quit. Nothing has changed in the rake task except for gems being updated that rely on this gem.

[jacob-hedengren]

Same issue here. Updated system gems today. Anyone got a solution for this?

[Fustrate]

I've looked to see if there's a way to blacklist a gem from my system, but my searches have come up empty. It's getting old having to add && gem uninstall fileutils =/

Maybe 1.1.0 needs to be yanked until this problem can be fixed?

[qortex]

Ran into this, and the solution here works: https://stackoverflow.com/questions/51334732/rails-5-2-0-with-ruby-2-5-1-console-warning-already-initialized-constant

I understand 1.0.2 stays installed as the default, 1.1.0 being installed too. Hence the issue.

When installed automatically, I get the warnings. Following command shows (new rails app, 2.5.1) :

gem list | grep fileutils
fileutils (1.1.0, default: 1.0.2)

Then doing:

gem uninstall fileutils
gem update fileutils --default

makes the warnings disappear. And btw, it shows:

gem list | grep fileutils
fileutils (default: 1.1.0, default: 1.0.2)

Hope it will help fixing this annoyance. Sorry I cannot be of more help, not really a wizard with those versioning topics!

[qortex]

I see there is a pull request which seems to indicate it deals with this specific issue. Anyone?

[jabbett]

Thanks @MicMicMon!

I use rvm, so I had to rvm gemset use global first before following your instructions.

[reitzig]

Persists after an update to

fileutils (1.2.0, default: 1.0.2)

@MicMicMon's workaround is still effective. Thanks!

[Fudoshiki]

rvm install 2.6
rvm 2.6@global
gem update
gem list

fileutils (1.2.0, default: 1.1.0)

some issue

temp solution
gem uninstall fileutils
gem update fileutils --default
gem list

fileutils (default: 1.2.0, default: 1.1.0)

[hadees]

@Fudoshiki I actually just ran gem uninstall fileutils to fix it. It must be loading from somewhere else, didn't have to reinstall it with -default.