On Mon, 16 Dec 2019 at 02:22, Sam Ruby <ru...@intertwingly.net> wrote:
> On Sun, Dec 15, 2019 at 7:33 PM sebb <seb...@gmail.com> wrote: > > > > Great, that seems to have fixed it. > > > > However the question is: how did the gems get there? > > > > I assume they must have been added recently, as the error only seems to > > have started Dec 15 @ 15:57 or a bit earlier which was when NodePing > > complained. > > Those were rather old versions of the gems, so I presume they were > installed when I set up whimsy-vm4. I assume something else changed > in the environment that caused that version of the gem to fail, but > isn't problematic with some later version. > > But that's just a theory. What exactly changed and why it only > affected svn update of all things is a mystery to me. > > Also git pull; I assume it was rake that was affected. > All in all, I think it would be best if we avoided rvm (and rbenv) > going forward. Less moving parts. > > Agreed; the fewer the better. And the less for people to learn (I've not used rvm or rbenv). > > S. > > - Sam Ruby > > > On Mon, 16 Dec 2019 at 00:15, Sam Ruby <ru...@intertwingly.net> wrote: > > > > > Found another one: > > > > > > root@whimsy-vm4:~# /usr/local/rvm/bin/rvm 2.4.1@global do gem > > > uninstall rubygems-bundler > > > Successfully uninstalled rubygems-bundler-1.4.4 > > > > > > - Sam Ruby > > > > > > On Sun, Dec 15, 2019 at 7:02 PM Sam Ruby <ru...@intertwingly.net> > wrote: > > > > > > > > On Sun, Dec 15, 2019 at 6:28 PM sebb <seb...@gmail.com> wrote: > > > > > > > > > > Hasn't worked ... > > > > > > > > Found and removed from @global: > > > > > > > > rubygems-bundler (1.4.4) > > > > > > > > Note that the version number matches the error below. > > > > > > > > - Sam Ruby > > > > > > > > P.S. I don't believe that whimsy-vm5 will need rvm. > > > > > > > > > > > > > On Sun, 15 Dec 2019 at 23:16, sebb <seb...@gmail.com> wrote: > > > > > > > > > > > On Sun, 15 Dec 2019 at 23:12, Sam Ruby <ru...@intertwingly.net> > > > wrote: > > > > > > > > > > > >> On Sun, Dec 15, 2019 at 6:03 PM sebb <seb...@gmail.com> wrote: > > > > > >> > > > > > > >> > Both are failing with: > > > > > >> > > > > > > >> > /usr/local/rvm/gems/ruby-2.4.1@global > > > > > >> > /gems/rubygems-bundler-1.4.4/lib/rubygems-bundler/noexec.rb:84:in > > > > > >> > `setup': undefined method `plain_specs' for > > > > > >> > #<Bundler::RubygemsIntegration:0x000000021891b8> > (NoMethodError) > > > > > >> > from /usr/local/rvm/gems/ruby-2.4.1@global > > > > > >> > /gems/rubygems-bundler-1.4.4/lib/rubygems-bundler/noexec.rb:124:in > > > > > >> > `check' > > > > > >> > > > > > >> > > > > > >> > > > > https://stackoverflow.com/questions/19849978/any-rails-command-gives-noexec-rb75in-setup-undefined-method-name > > > > > >> suggests: > > > > > >> > > > > > >> $ rvm @global > > > > > >> $ gem uninstall bundler > > > > > >> > > > > > >> I logged in and issued those commands. Let's see if that helps. > > > > > >> > > > > > >> > > > > > > Thanks! > > > > > > > > > > > > I also rebooted, as a reboot was overdue. > > > > > > Should find out at 23:20 UTC if the rake commands now work. > > > > > > > > > > > > > > > > > >> > Other parts of Whimsy seem to be working. > > > > > >> > > > > > > >> > S. > > > > > >> > > > > > >> - Sam Ruby > > > > > >> > > > > > > > > > >
