Open honood opened 2 months ago
I presume the .lock
files do not need any gem wrapper. I found the output so much distracting that I temporarily commented out the warning message:
sed -i "s/warn \"GemWrappers: Can not wrap not executable file: #{target_path}\"/# warn \"GemWrappers: Can not wrap not executable file: #{target_path}\"/g" ~/.rvm/rubies/ruby-3.3.5/lib/ruby/gems/3.3.0/gems/gem-wrappers-1.4.0/lib/gem-wrappers/installer.rb
Obviously, a more proper fix would be to ignore the lock files somehow.
I went a even more drastic way, as I don't need wrappers, and I surely hadn't installed the wrapper gem manually so it must have been installed by rvm
, I just ended uninstalling it:
gem uninstall -i ~/.rvm/rubies/ruby-3.3.5/lib/ruby/gems/3.3.0 gem-wrappers
RubyGems 3.5.19 and Bundler 2.5.19 remove the .lock
files that trigger the warnings from GemWrappers.
RubyGems 3.5.19 and Bundler 2.5.19 remove the
.lock
files that trigger the warnings from GemWrappers.
didn't fix the problem for me ...
$debian: bundler -v
Bundler version 2.5.19
$debian: gem -v
3.5.19
$debian: gem install ruby-lsp -v 0.18
Fetching ruby-lsp-0.18.0.gem
GemWrappers: Can not wrap not executable file: /home/.../bin/irb.lock
GemWrappers: Can not wrap not executable file: /home/.../bin/rdoc.lock
GemWrappers: Can not wrap not executable file: /home.../bin/ri.lock
Successfully installed ruby-lsp-0.18.0
Parsing documentation for ruby-lsp-0.18.0
Installing ri documentation for ruby-lsp-0.18.0
Done installing documentation for ruby-lsp after 0 seconds
1 gem installed
@martinbarilik I'd let RubyGems know there's still an issue. After a very quick read through of the code, I don't think this is a problem with GemWrappers - it's just warning that it's seeing unexpected files.
If anyone else is having this issue, the fix seems to be to get the .lock files removed. If you're still having trouble, a workaround is to manually remove the .lock files, in the directory that is reported in the warning.
@martinbarilik I'd let RubyGems know there's still an issue. After a very quick read through of the code, I don't think this is a problem with GemWrappers - it's just warning that it's seeing unexpected files.
If anyone else is having this issue, the fix seems to be to get the .lock files removed. If you're still having trouble, a workaround is to manually remove the .lock files, in the directory that is reported in the warning.
Removing the .lock files eliminated the warnings for me. Thanks.
After installing Ruby 3.3.5, I got the following many warning messages like the following when updating or installing gems:
The installed
gem-wrapper
is1.4.0
.