Fpm: Unable to install fpm due to childprocess issue

Created on 30 Jan 2019 · 10Comments · Source: jordansissel/fpm

Attempting to install FPM today fails with:

Fetching: childprocess-1.0.0.gem (100%)
Building native extensions.  This could take a while...
ERROR:  Error installing fpm:
        ERROR: Failed to build gem native extension.

    current directory: /var/lib/gems/2.3.0/gems/childprocess-1.0.0/ext
/usr/bin/ruby2.3 mkrf_conf.rb

current directory: /var/lib/gems/2.3.0/gems/childprocess-1.0.0/ext
/usr/bin/ruby2.3 -rubygems /usr/share/rubygems-integration/all/gems/rake-10.5.0/bin/rake RUBYARCHDIR=/var/lib/gems/2.3.0/extensions/x86_64-linux/2.3.0/childprocess-1.0.0 RUBYLIBDIR=/var/lib/gems/2.3.0/extensions/x86_64-linux/2.3.0/childprocess-1.0.0
/usr/bin/ruby2.3: No such file or directory -- /usr/share/rubygems-integration/all/gems/rake-10.5.0/bin/rake (LoadError)

rake failed, exit code 1

Gem files will remain installed in /var/lib/gems/2.3.0/gems/childprocess-1.0.0 for inspection.
Results logged to /var/lib/gems/2.3.0/extensions/x86_64-linux/2.3.0/childprocess-1.0.0/gem_make.out

This appears to be related to a new version of childprocess released today.

Raised upstream as https://github.com/enkessler/childprocess/issues/143

Source

fatmcgav

👍4

Most helpful comment

fpm 1.11.0 released.

This is possibly still in progress, but it looks like you normally git tag upon release. I noticed there isn't a 1.11 tag or changelog entry.

andrewkroh on 31 Jan 2019

👍2

All 10 comments

If possible, the dependency versions should be fixed, or restricted to the major version (dependencies bumping a major version should be reviewed manually).

Workaround: gem install childprocess --version 0.9.0 before gem install --no-ri --no-rdoc fpm

benma on 30 Jan 2019

I'm working on this now to pin a version.

jordansissel on 30 Jan 2019

fpm 1.11.0 released.

jordansissel on 30 Jan 2019

🎉2

fpm 1.11.0 released.

This is possibly still in progress, but it looks like you normally git tag upon release. I noticed there isn't a 1.11 tag or changelog entry.

andrewkroh on 31 Jan 2019

👍2

Oops! I had limited time yesterday and forgot to tag, but I do remember
updating the changelog. I’ll work on that today.

On Thu, Jan 31, 2019 at 8:07 AM Andrew Kroh notifications@github.com
wrote:

fpm 1.11.0 released.

This is possibly still in progress, but it looks like you normally git tag
upon release. I noticed there isn't a 1.11 tag or changelog entry.

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
https://github.com/jordansissel/fpm/issues/1592#issuecomment-459401348,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIC6tMR5SLt7FGx7cc-K6I4CVqyK2lwks5vIxS3gaJpZM4aadK2
.

jordansissel on 31 Jan 2019

@jordansissel Hi Jordan, unfortunately this has caused a new problem when converting fpm to an RPM and then attempting to install it on CentOS 7. The latest version of rubygem-childprocess available in the epel repo is is 0.5.3. As fpm works fine with the older version of childprocess, can the gemspec say: spec.add_dependency("childprocess", "~> 0.5")? This will still prevent childprocess 1.0.0 from being installed, but will mean fpm can still work with the older version of childprocess.

I understand if you don't care about this as it is a slightly fringe interest. If you won't fix it, I can manually tweak the dependencies of the converted fpm RPM.

liger1978 on 1 Feb 2019

I am ok relaxing the dependency constraint. Would you mind sending a PR for
that? I will merge and cut another release

On Fri, Feb 1, 2019 at 11:51 AM liger1978 notifications@github.com wrote:

@jordansissel https://github.com/jordansissel Hi Jordan, unfortunately
this has caused a new problem when converting fpm to an RPM and then
attempting to install it on CentOS 7. The latest version of
rubygem-childprocess available in the epel repo is is 0.5.3. As fpm works
fine with the older version of childprocess, can the gemspec say: spec.add_dependency("childprocess",
"~> 0.5")? This will still prevent childprocess 1.0.0 from being
installed, but will mean fpm can still work with the older version of
childprocess.

I understand if you don't care about this as it is a slightly fringe
interest. If you won't fix it, I can manually tweak the dependencies of the
converted fpm RPM.

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/jordansissel/fpm/issues/1592#issuecomment-459846573,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIC6ojcapYIfO2KxVK2fw9SizYHVEt0ks5vJJq6gaJpZM4aadK2
.