Could not find gem 'puma' in https://github.com/rails/rails.git (at 5-2-stable@92fd1c2).
    The source does not contain any versions of 'puma'

In this example, we're making sure that `view` is available in global
config hooks.

`group.run` accepts a reporter, but it defaults to a NullReporter
anyway.

2.2 support has been dropped from 1.5.2
https://rubygems.org/gems/i18n/versions/1.5.2
https://rubygems.org/gems/i18n/versions/1.5.1

When installed from scratch on 2.2.10 with RubyGems 2.3.10 and Bundler
1.17.3, with RAILS_VERSION set to `5-2-stable`:

    childprocess-3.0.0 requires ruby version >= 2.3.0, which is incompatible with the current version, ruby 2.2.10p489
    xpath-3.2.0 requires ruby version >= 2.3, which is incompatible with the current version, ruby 2.2.10p489
    i18n-1.8.3 requires ruby version >= 2.3.0, which is incompatible with the current version, ruby 2.2.10p489
    nio4r-2.5.2 requires ruby version >= 2.3, which is incompatible with the current version, ruby 2.2.10p489
    rack-2.2.3 requires ruby version >= 2.3.0, which is incompatible with the current version, ruby 2.2.10p489
    public_suffix-4.0.5 requires ruby version >= 2.3, which is incompatible with the current version, ruby 2.2.10p489
    rubyzip-2.3.0 requires ruby version >= 2.4, which is incompatible with the current version, ruby 2.2.10p489

    sprockets-4.0.2 requires ruby version >= 2.5.0, which is incompatible with the current version, ruby 2.2.10p489

We had sprockets capped, but only for `'~> x.x.x'`/`x.x.x` formats.

`set -e` stops the script when a *simple command* fails.
If the command is part of an `||`-expression, the script continues.

It seems unessential that we fail to uninstall `bundler` from the global
gemset, the build is green after all.

    actionpack was resolved to 3.2.22.5, which depends on
      sprockets (~> 2.2.1)

    Warning: unrecognized cop BinaryOperatorParameterName found in /home/travis/build/rspec/rspec-rails/.rubocop_rspec_base.yml

RucoCop on CI is fixed at 0.23, and has outdated cop names.
Even without those disabling, `rubocop lib` passes just fine.

    Gem::RuntimeRequirementNotMetError: public_suffix requires Ruby version >= 1.9.3. The current ruby version is 1.8.
    An error occurred while installing public_suffix (1.4.2), and Bundler cannot continue.

    Gem::RuntimeRequirementNotMetError: redcarpet requires Ruby version >= 1.9.2. The current ruby version is 1.8.
    An error occurred while installing redcarpet (3.1.1), and Bundler cannot continue.

    Gem::RuntimeRequirementNotMetError: rubyzip requires Ruby version >= 1.9.2. The current ruby version is 1.8.
    An error occurred while installing rubyzip (1.0.0), and Bundler cannot continue.

Update to the latest released Rails 5.2.4.3 didn't help, it still has
the bug.

Backported from https://github.com/rspec/rspec-rails/blob/c0a8c22186a1232e3b1612c44bc88052ec56c945/spec/rspec/rails/example/view_example_group_spec.rb#L239

For the reasons described in the comment

bundle exec rails new ./tmp/example_app --no-rc --skip-javascript --skip-bootsnap --skip-sprockets --skip-git --skip-test-unit --skip-listen --skip-bundle --template=example_app_generator/generate_app.rb

    Gem::RuntimeRequirementNotMetError: spring requires Ruby version >= 2.4.0. The current ruby version is 2.3.0.
    An error occurred while installing spring (2.1.0), and Bundler cannot continue.

ffi has strict Ruby constraints

aruba:

    Bundler could not find compatible versions for gem "thor":
      In Gemfile:
        aruba (~> 0.14.11) was resolved to 0.14.12, which depends on
          thor (~> 0.19)

        rails (~> 3.1.12) was resolved to 3.1.12, which depends on
          railties (= 3.1.12) was resolved to 3.1.12, which depends on
            thor (~> 0.14.6)

https://github.com/rspec/rspec-rails/pull/2140/files#diff-73c25cf975ccb4c89d8659202506c353L58
bumped aruba from 0.5.4 straight to 0.14.12. Using the version that used
to work for older rails.

There's a minor difference:

    Widget management
      User creates a new widget

    -1 example, 0 failures, 1 pending
    +1 example, 0 failures

most probably caused by 5-2-stable vs 5.2.4.x spec generation
difference.

Co-authored-by: Jon Rowe <hello@jonrowe.co.uk>