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
I'm not entirely sure if this is an issue with Pkgr or the buildpack. The issue I'm having is that I build an RPM with Pkgr from a Rails application. When I install the RPM I can see that the installed files don't have the same permissions as the original files.
I've done some debugging, like running fpm with the --debug-workspace flag, which keeps the workspace after the packaging is complete. I can see that the files have the wrong permission in the workspace. I've also tried to run fpm manually to package a simple directory with a file. That will not change the permission of the file. So it looks like it's not fpm that changes the permissions.
Is it Pkgr that changes the permissions? If that's the case, is that intentional?
Most files end up with the -rwxr-xr-t permission instead of -rw-r--r--. It adds executable permission and sets the sticky bit.
The text was updated successfully, but these errors were encountered:
It applies to all files. For example, the readme file I have in the root directory of the project. I'm using CentOS 6. This is from the debug output, the Pkgr::Config instance:
I'm not entirely sure if this is an issue with Pkgr or the buildpack. The issue I'm having is that I build an RPM with Pkgr from a Rails application. When I install the RPM I can see that the installed files don't have the same permissions as the original files.
I've done some debugging, like running
fpm
with the--debug-workspace
flag, which keeps the workspace after the packaging is complete. I can see that the files have the wrong permission in the workspace. I've also tried to runfpm
manually to package a simple directory with a file. That will not change the permission of the file. So it looks like it's notfpm
that changes the permissions.Is it Pkgr that changes the permissions? If that's the case, is that intentional?
Most files end up with the
-rwxr-xr-t
permission instead of-rw-r--r--
. It adds executable permission and sets the sticky bit.The text was updated successfully, but these errors were encountered: