Ugh, so literally had thought I had cleared up my problem with install ruby on rails but now I’m running into issues with
gem install rails
gem update --system
Attached is a screenshot of what the commands return. I’ve been stuck on this problem for awhile now. I’ve tried uninstalling both ruby and rails, I’ve also tried just deleting the executables ruby and rails from /usr/bin in addition to the ruby-mri gem.
Any suggestions for how to move forward? End goal is to just get Ruby on Rails re-installed.
So, ideally one should not mix system installed packages (ones installed from the repositories) and ones installed from various forges. One should also not delete files from these packages by hand. rpm (via dnf) manages them, and users should use these tools only.
To update gem, which is /usr/bin/gem and is a system installed file, when you run gem update --system, you probably need to run it using sudo. I would STRONGLY advise against doing so. If at all possible, we should check if the rpm packages in the repository provide a newer version.
Ah, so part of the problem is that you are running Fedora 26. Fedora 26 reached its End of Life (EOL) quite a while ago and does not receive updates any more. It is why you are not receiving the latest version of ruby.
That’s not a wise decision really—Fedora 26 being EOL also implies that it will no longer receive security updates. If you are looking for a slower moving system to user for work, one of the Fedora downstreams, like CentOS, would be suggested. Each Fedora release only lives for 13 months and them must be upgraded for the next one.
You’ll have to find other ways of installing these tools since you will no longer be able to rely on the Fedora repositories. sudo gem update --system etc. will be the only way. You’ll have to keep track of what you’re installing etc. yourself, though, since rpm/dnf will not be able to track these.
I see that the last line says to add --allowerasing to replace conflicting packages or --skip-broken to skip uninstalled packages but if I do any of these options, will this come back to bite me later on?
But then again I’m not trying to upgrade to “Rawhide” so that’s probably not the command I should use.
At this point, I’m not really sure if I should just ignore the warning and proceed forward or if I should try and “fix” the warning and then proceed forward. However, if I were to “fix” the warning, I am not sure what the next step should be.
Fedora 26 doesn’t have the keys for Fedora 30, because they never existed at the same time. Generally, the only supported upgrade path is N+1 or N+2. So if possible, it might be easier to upgrade to 26->27->28->29->30 individually or 26->28->30, though unfortunately it will be a bit slower.