-s dir says 'File name too long'
#174
Comments
|
hah, hilarious. I'll take a peek |
|
Slightly modified (changed the directory, really) Works for me in fpm 0.4.1 One other slight change I made was that instead of this: I do this: |
|
Can you test 0.4.1 (available on rubygems) and let me know if this problem persists? |
|
Yep, still busted. |
|
Confirmed I can reproduce this when -C flag is not used. |
|
This probably has to do with $PWD being used internally in fpm for temp dir locations. |
|
Does this gem work for you? http://semicomplete.com/files/fpm/fpm-0.4.2rc1.gem |
|
It does! |
|
woot. I changed from using $PWD to using the default temp directory (/tmp, probably). I'll see about making a flag to set the temp directory and push out a new release. Thanks much for testing! :) |
|
Thanks for the great software! |
|
fpm 0.4.2 released with this fix. |
|
having a similar issue with the latest version.... command is fpm -s dir -t deb -a amd64 -C with the error (shortened....) |
|
To add to this thread, I just got the Errno::ENAMETOOLONG on version 1.8.1. I had "--workdir ./tmp" specified. Changing it to "--workdir $PWD/tmp" worked around the issue. |
|
I am also experiencing this bug when I to use fpm in a Jenkins 2 Docker build container (for the uninitiated, Jenkins 2 containerises each job's build environment nowadays) to make an RPM. I have tried specifying an absolute path for the workdir, tried doing a workdir of $PWD/tmp, and leaving workdir unspecified, but none of this works. I think the build container messes with the PATH or PWD in some way (though not an obvious way - PWD just gives me /var/lib/Jenkins/jobs/my-job/workspace), and this breaks FPM. Anyone else experiencing problems with FPM + Jenkins2 + -s dir? |
Sample command line:
That gives me:
But if I run
fpmfrom one level up and use-C 1.7.9.4/ ., it works fine.This is on a Ubuntu 12.04 Beta 1 64-bit server, fwiw.
The text was updated successfully, but these errors were encountered: