-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
ERROR: While executing gem ... (ArgumentError) wrong number of arguments (given 4, expected 1) #4976
Comments
Hi! The problem is that you're using an old version of rubygems that does not support psych 4. Uninstalling Alternatively you can upgrade rubygems with Hope this helps! |
Greetings @deivid-rodriguez , Thanks for your support! So I tried to update the gems. That didn't work and gave me the same error so I followed your link and updated the gem as sudo user.
Looks like I gotta turn to Microsoft here? Not sure yet on that. Anyway I did as you suggested and Uninstalled psych. And then ran
Ok I go to that log. Forgive me, I don't use WSL2 that much or Linux CLIs for that matter. Maybe I should learn how to use it more? I'm sure if that would even solve this error. Anyway here is the mkmf.log it mentioned.
I googled the error in that log file and got this SO link These fixes are making me a little anxious as they involve changing the permissions of the route folder. I'm looking for your opinion on that before I try one of these fixes, please. Should I try to back up my Ubuntu WSL instance first before I continue? Sorry for long message. |
Hello @LayersOfAbstraction, sorry you're still having trouble. Unfortunately the page I linked to was pretty misleading. The idea was that you downloaded the latest version manual, check it out into some directory, and then run Anyways, I believe that Now, after uninstalling Regarding the new issue, it seems like RMagick needs either |
Hi again @deivid-rodriguez Yeah I installed the suggested package as sudo. Then tried to install the jekyll-responsive-image library. Got a a very similar error to the one before this time it mentioned something about MagickCore saying
Ruby could not locate |
Ok I've been able to |
Hello @deivid-rodriguez and @LayersOfAbstraction I was butting my head up against this tonight. I'm getting Jekyll up and running on WSL2 myself and noted why gem update --system is having conniptions with WSL2 systems. WSL2 layers Linux on top of Windows, part of how it does that is it treats the Windows C: as a /mnt point. For interaction between the two, the security permissions of /mnt/c cannot be changed to I'm not certain exactly how to get around that, but pretty certain this is the pain point for this issue. The particular message that points to this is:
|
Error was: ERROR: While executing gem ... (ArgumentError) wrong number of arguments (given 4, expected 1) Error: Process completed with exit code 1. Upstream issue is: rubygems/rubygems#4976
What did you do?
I ran the command
bundle update
after inserting the jekyll-responsive-image plugin into my_config.yml
file and theGemfile
and created the files for it in my_plugins
and_includes
directories.I ran this on WSL2. Using Ruby 2.5 and Jekyll libraries installed from this link
What did you expect to happen?
I expected Bundler to to be able to rebuild the application and for
gem install jekyll-responsive-image
to install the library for me to dynamically resize the image.What happened instead?
I could not install the library.
Here's the packages it started fetching.\
Fetching gem metadata from http://rubygems.org/.......... Resolving dependencies... Using public_suffix 4.0.6 Using http_parser.rb 0.6.0 Using colorator 1.1.0 Using eventmachine 1.2.7 Using bundler 2.2.17 Using rb-fsevent 0.11.0 Using forwardable-extended 2.6.0 Fetching concurrent-ruby 1.1.9 (was 1.1.8) Using rexml 3.2.5 Using liquid 4.0.3 Fetching rouge 3.26.1 (was 3.26.0) Using mercenary 0.4.0 Fetching ffi 1.15.4 (was 1.15.0) Fetching rmagick 4.2.2 Fetching addressable 2.8.0 (was 2.7.0) Fetching wdm 0.1.1 Using safe_yaml 1.0.5 Using kramdown 2.3.1 Using em-websocket 0.5.2 Using pathutil 0.16.2 Using kramdown-parser-gfm 1.1.0 Fetching unicode-display_width 1.8.0 (was 1.7.0)
Then...
KABOOM, the balance of the universe destroyed itself. I could see this error.
Backtrace
Environment
Bundler Build Metadata
Gemfile
Gemfile
Gemfile.lock
Absolutely. I tried upgrading to Ruby 2.7 in hopes that would solve the problem. But can't use it while I have that error. Also went here
And tried to uninstall psych which just gave me another error so I reinstalled psych.
Yes, couldn't find anything related to this error.
The text was updated successfully, but these errors were encountered: