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
The problem is (I think) that fpm dependency specification is too loose. It allows the latest ffi and git gem dependencies while when actually trying to install the latest version of these dependencies, they fail because those gems rely on ruby 2.3 and RHEL7 based distros use ruby2.0.
The latest version of the git gem requires ruby >= 2.3, which
is too new for the default ruby 2.0 on CentOS 7 and ruby 2.1 on openSUSE 42.
jordansissel/fpm#1742
The problem is (I think) that fpm dependency specification is too loose. It allows the latest ffi and git gem dependencies while when actually trying to install the latest version of these dependencies, they fail because those gems rely on ruby 2.3 and RHEL7 based distros use ruby2.0.
On a fresh CentOS7 AWS instance:
And this happens:
The workaround is:
So that fpm uses older versions of gems instead of the latest versions that rely on ruby 2.3.
I think a better solution is to detect ruby 2.0 and then constrain the ruby gem dependency versions to supported version.
The text was updated successfully, but these errors were encountered: