(12:17:10 AM) davereid: Odd...never had this problem before. Whenever I commit files to CVS on d.org, it's changing the permissions on the files locally. So I get fatal errors on my local D6-dev install because it couldn't read files for inclusion.
(12:31:29 AM) davereid: I think the files in CVS repositories have their permissions limited. Whenever we commit or checkout, we get non-readable files by default.
(12:32:48 AM) davereid: See http://durak.org/sean/pubs/software/cvsbook/CVS-keeps-changing-file-perm...
Basically my files are being changed from 744 to 740, so .module files etc. are no longer readable by the www-data user since I'm the owner of the files. This problem started after my account was reset after the CVS server crack down. Is it possible that the files are so locked down on the CVS server that they're unusable for the rest of us when we checkout/commit? What's going on?
Comments
Comment #1
Anonymous (not verified) commentedI just confirmed this: all contrib checked out from CVS (modules, profiles etc) have files with 640. However my directories are 755 as expected. Maybe some sort of umask issue on the CVS server? Though this has only just started happening, on modules that I know have had no commits in 5 days.
Comment #2
dave reidIt doesn't even make sense for these files to be locked down. They're viewable by anyone from WebCVS, so it makes no sense. Only hindering people's ability to contribute to Drupal using an already frustrating VCS. :)
Comment #3
gregglesGuys - nnewton and killes were up late last night working long hours insuring the safety of our various servers and repositories - let's be a little patient on this issue.
Comment #4
dave reidComment #5
dave reid@greggles: I know, I was talking with nnewton last night and they did a great job responding to the security threat (and the stupid user who caused it). But this is a big problem for anyone using CVS (not as much as having your password stolen though), so I created an issue and am explaining why it's not reasonable to have those permissions if it was intentional (which it probably wasn't).
Comment #6
dave reidnnewton fixed the file permissions on cvs.drupal.org and I can confirm committing files doesn't remove the read-only for all users.
Comment #7
nnewton commentedHi all,
My apologies for this. It should be fixed now.
-N