Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign uptsd --save flag modifies permissions of parent directories unnecessarily #125
Comments
referenced
this issue
in misak113/tsd
Apr 23, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
vchrm
Jul 28, 2015
Unfortunately others do run into the same thing. We have been struggling with this issue for months now. After each tsd call (from cli as well as with gulp-tsd) we need to change permissions to our own folders back again :-(.
My only question is: Why does tsd have to touch the permissions at all? Default mkdir() call creates the directory under default permissions (given by process' umask). Why is not this sufficient?
vchrm
commented
Jul 28, 2015
|
Unfortunately others do run into the same thing. We have been struggling with this issue for months now. After each tsd call (from cli as well as with gulp-tsd) we need to change permissions to our own folders back again :-(. My only question is: Why does tsd have to touch the permissions at all? Default mkdir() call creates the directory under default permissions (given by process' umask). Why is not this sufficient? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
igorbt
commented
Aug 11, 2015
|
The same happens in our setup. Any chance this bug will be fixed soon? |
karmux
referenced this issue
Jan 16, 2016
Closed
tsd install changes permissions for current directory #262
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
karmux
commented
Jan 16, 2016
|
Spent also several hours debugging this. |
joshuacc commentedFeb 12, 2015
Using tsd
0.6.0-beta.5.I have a directory structure that looks like this:
/var/www/applications/my-app/tsd.json. Anytime I run tsd with the--saveflag, it sets themy-appfolder's permissions to744. As a result, the apache user can no longer execute the application contained inmy-app.The problem appears to be caused by this line.
I can probably put together a pull request to fix the issue, but in order to do so, I have a couple of questions.
u+win order to guarantee write permissions exist?I spent quite a while (several days) on this seemingly random failure, and want to make sure others don't run into the same thing.😄
Thanks!