| View previous topic :: View next topic |
| Author |
Message |
Rockman8
n00b
Joined: 19 Sep 2023
Posts: 38
|
 Posted: Fri Nov 08, 2024 3:29 am Post subject: [rubyGEMS] Doubt on how to manage portage and gems. |
 |
|
Hello,
I'm running vagrant and I got an issue relating to excon
excon-0.104.0 is currently installed via portage
| Code: | eix excon
[I] dev-ruby/excon
Available versions: 0.104.0^t ~0.112.0^t {doc test RUBY_TARGETS="ruby31 ruby32 ruby33"}
Installed versions: 0.104.0^t(11:26:45 10/07/24)(-doc -test RUBY_TARGETS="ruby32 -ruby31")
Homepage: https://github.com/excon/excon
Description: EXtended http(s) CONnections |
and I got an updated version on gem
| Code: | gem list excon
*** LOCAL GEMS ***
excon (1.2.0, 0.104.0)
|
Now when I try running vagrant up I get this
| Code: | Vagrant failed to initialize at a very early stage:
The plugins failed to initialize correctly. This may be due to manual
modifications made within the Vagrant home directory. Vagrant can
attempt to automatically correct this issue by running:
vagrant plugin repair
If Vagrant was recently updated, this error may be due to incompatible
versions of dependencies. To fix this problem please remove and re-install
all plugins. Vagrant can attempt to do this automatically by running:
vagrant plugin expunge --reinstall
Or you may want to try updating the installed plugins to their latest
versions:
vagrant plugin update
Error message given during initialization: Unable to activate fog-core-2.6.0, because excon-0.104.0 conflicts with excon (~> 1.0) |
| Code: | | Error message given during initialization: Unable to activate fog-core-2.6.0, because excon-0.104.0 conflicts with excon (~> 1.0) |
I got 2 versions conflicting because 1 is installed via portage and another updated one is on gem.
Can I safely remove the outdated one from portage without breaking anything?
And I just happened to run will this interfere with portage when I try to run | Code: | | emerge -avuDN @world |
If it does what are the measures I should be taking to prevent the installed gems /usr/local/lib64/ruby/gems/3.2.0 from interfering with emerge -avuDN @world?
edit:
| Code: | | for gem in $(sudo gem list --no-versions | tr '\n' ' '); do sudo gem uninstall -aIx $gem; done |
The folder
| Code: | | /usr/local/lib64/ruby/gems/3.2.0/gems |
is empty now.
Although excon 1.2.0 has been uninstalled and the portage version 0.104.0 remains this error still persists
| Code: | | Error message given during initialization: Unable to activate fog-core-2.6.0, because excon-0.104.0 conflicts with excon (~> 1.0) |
and installing excon-1.2.0 without sudo gives the same error.
Thanks in advance |
|
| Back to top |
|
 |
Rockman8
n00b
Joined: 19 Sep 2023
Posts: 38
|
| Posted: Tue Nov 12, 2024 5:10 am Post subject: |
|
|
My guess is that when Ruby was upgraded a new folder was made on `/home/USER/.vagrant.d/gems/` and I realized that the contents from the version before (3.2.4) had some content in and it was from a few months ago while the 3.2.5 was just made and totally empty,
Copied all the contents from the previous version to the new folder and that was it.
As to why I was unable to reinstall all the things I had on another folder, I got no idea. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
