https://bugs.kde.org/show_bug.cgi?id=404102
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |NOT A BUG
Status|REPORTED |RESOLVED
--- Comment #1 from Harald Sitter <sit...@kde.org> ---
Ruby 2.1 is EOL for more than 2 years.
I am going to great lengths to keep compatibility and require only core ruby
features, but unfortunately much of the wider ecosystem has moved on and
introduced incompatibilities so testing our 2.1 comaptibility is actually not
viable anymore. You can manually hack the version check to allow 2.1 or, use
rbenv or rvm to provision a newer ruby isolated from your systems (which is
what I recommend), or use a docker/lxd container with an actually supported
ruby.
I appreciate that this is very annoying but the motivation behind the tight
version locking is to ensure that the generate tarballs are in fact going to be
exactly what we intend them to be, so if we can't test that I'd rather tighten
the compatibility lock than allow potentially broken tarballs getting released
on account of us the unit test suite not running on unsupported ruby versions.
--
You are receiving this mail because:
You are watching all bug changes.
