You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to updated dependencies of the machinery Centos 7 and Ubuntu 18.04 LTS are out of the game for machinery. On Centos issue is ruby, because it would need to be at least 2.3 or more.
It works on Centos 8 as per installation instructions.
The text was updated successfully, but these errors were encountered:
On paper Machinery still only requires Ruby version 2.0 s.required_ruby_version = '>= 2.0.0' but the problem is that many gems, which are pulled in as dependency by Machinery, require newer Ruby versions nowadays.
You can checkout machinery with git, check out which gems result in problems and restrict the versions of them to an older version in the Gem configuration files.
I am pretty sure that there are a lot of direct and indirect dependencies which would need to be restricted so it is not a trivial task.
In general it should be much easier to run Machinery on a newer system or in a vm/docker and just inspect the older ones remotely.
I am not sure there is much we can do except of restricting all gems to ancient versions which would potentially have security implications for everyone, even the ones with newer systems.
Hello!
Due to updated dependencies of the machinery Centos 7 and Ubuntu 18.04 LTS are out of the game for machinery. On Centos issue is ruby, because it would need to be at least 2.3 or more.
It works on Centos 8 as per installation instructions.
The text was updated successfully, but these errors were encountered: