Comment # 4 on bug 1204481 from Santiago Zarate

(In reply to Santiago Zarate from comment #3)
> (In reply to Josef Reidinger from comment #2)
> > (In reply to Marcus Meissner from comment #1)
> > > testcase is super simple:
> > > 
> > > zypper -n in --recommends -C "rubygem(rails)"
> > > rails new mycoolapp --skip-bundle --skip-test
> > > cd mycoolapp
> > > (rails server -b 0.0.0.0 &)
> > > for i in {1..100} ; do sleep 0.1; curl -s http://localhost:3000 | grep
> > > "<title>Ruby on Rails" && break ; done
> > > pkill -f "rails server" || pumactl -P tmp/pids/server.pid stop
> > > 
> > > 
> > > the rails server start up fails with:
> > > (rails server -b 0.0.0.0 &) 
> > > Could not find gem 'puma (~> 3.11)' in any of the gem sources listed in your
> > > Gemfile.
> > > Run `bundle install` to install missing gems.
> > > 
> > > 
> > > I have however installed ruby2.5-rubygem-puma-4.3.12-150000.3.9.1.x86_64
> > 
> > and that is issue ~> 3.11 means > 3.11 but < 4.0 so 4.3 is too high to
> > satisfy that dependency -
> > https://thoughtbot.com/blog/rubys-pessimistic-operator
> 
> So we're distributing two gems that aren���t compatible?

Even if we move the version of puma further, we'll end up in a similar
situation with other gems:

> 247338f6210b:/mycoolapp # rails s
> Could not find gem 'listen (< 3.2, >= 3.0.5)' in any of the gem sources listed in your Gemfile.
> Run `bundle install` to install missing gems.