[BLOCKER] Incorrect permissions for Sass files on the dev server?

Are the commands to work with this theme documented anywhere so I can reproduce this?

Neil, I was able to reproduce the error by running compass watch . from the bluecheese theme folder. For ongoing development, this command is essentially the only one we use.

The command listens for changes to the sass folder, and recompiles the Sass files to legit CSS (residing in the css folder). So it watches for I/O then writes to disk each time we update anything within sass folder.

It seems like the .sass-cache folder is causing the problem in this instance, and it might be due to that directory being owned by Snugug instead of bender like the rest of them. I tried to chown but it won't let me change it.

[rupl@devwww bluechops]$ pwd
/var/www/dev/theme-drupal_7.redesign.devdrupal.org/htdocs/sites/all/themes/bluechops

[rupl@devwww bluechops]$ ls -la
total 80
drwxrwsr-x 10 bender     developers  4096 Jun 23 13:16 .
drwxrwsr-x  8 bender     developers  4096 May 17 18:17 ..
-rwxr--r--  1 lewisnyman developers  1152 Jun 23 13:16 bluechops.info
-rw-rw-r--  1 bender     developers   903 Jun 19 11:03 config.rb
drwxr-sr-x  2 lewisnyman developers  4096 Jun 23 21:43 css
drwxrwsr-x  8 bender     developers  4096 Jun 23 20:59 .git
-rw-rw-r--  1 bender     developers    62 May 23 02:36 .gitignore
-rw-rw-r--  1 bender     developers  5227 May 17 18:17 iepngfix.htc
drwxrwsr-x  3 bender     developers  4096 May 17 18:17 images
drwxrwsr-x  2 bender     developers  4096 May 17 18:23 js
drwxrwsr-x  3 bender     developers  4096 Jun 23 15:59 sass
drwxr-sr-x 11 snugug     developers  4096 Jun 15 19:59 .sass-cache
-rwxrw-r--  1 bender     developers 17925 Jun 23 18:18 template.php
drwxrwsr-x  3 bender     developers  4096 Jun 23 18:22 tpl
drwxrwsr-x  3 bender     developers  4096 May 17 18:17 widgets

[rupl@devwww bluechops]$ compass watch .
Errno::EACCES on line ["26"] of /usr/lib64/ruby/gems/1.9.1/gems/sass-3.2.0.alpha.244/lib/sass/cache_stores/filesystem.rb: Permission denied - /var/www/dev/theme-drupal_7.redesign.devdrupal.org/htdocs/sites/all/themes/bluechops/./.sass-cache/0a02f94371680231ecdcf940c3429303b7773df3/styles.scssc
Run with --trace to see the full backtrace

[rupl@devwww bluechops]$ compass watch --trace .
Errno::EACCES on line ["26"] of /usr/lib64/ruby/gems/1.9.1/gems/sass-3.2.0.alpha.244/lib/sass/cache_stores/filesystem.rb: Permission denied - /var/www/dev/theme-drupal_7.redesign.devdrupal.org/htdocs/sites/all/themes/bluechops/./.sass-cache/0a02f94371680231ecdcf940c3429303b7773df3/styles.scssc
  /usr/lib64/ruby/gems/1.9.1/gems/sass-3.2.0.alpha.244/lib/sass/cache_stores/filesystem.rb:26:in `_retrieve'
  /usr/lib64/ruby/gems/1.9.1/gems/sass-3.2.0.alpha.244/lib/sass/cache_stores/base.rb:62:in `retrieve'
  /usr/lib64/ruby/gems/1.9.1/gems/sass-3.2.0.alpha.244/lib/sass/cache_stores/chain.rb:25:in `block in retrieve'
  /usr/lib64/ruby/gems/1.9.1/gems/sass-3.2.0.alpha.244/lib/sass/cache_stores/chain.rb:24:in `each'
  /usr/lib64/ruby/gems/1.9.1/gems/sass-3.2.0.alpha.244/lib/sass/cache_stores/chain.rb:24:in `each_with_index'
  /usr/lib64/ruby/gems/1.9.1/gems/sass-3.2.0.alpha.244/lib/sass/cache_stores/chain.rb:24:in `retrieve'
  /usr/lib64/ruby/gems/1.9.1/gems/sass-3.2.0.alpha.244/lib/sass/engine.rb:327:in `_to_tree'
  /usr/lib64/ruby/gems/1.9.1/gems/sass-3.2.0.alpha.244/lib/sass/engine.rb:268:in `to_tree'
  /usr/lib64/ruby/gems/1.9.1/gems/sass-3.2.0.alpha.244/lib/sass/plugin/staleness_checker.rb:179:in `tree'
  /usr/lib64/ruby/gems/1.9.1/gems/sass-3.2.0.alpha.244/lib/sass/plugin/staleness_checker.rb:169:in `compute_dependencies'
  /usr/lib64/ruby/gems/1.9.1/gems/sass-3.2.0.alpha.244/lib/sass/plugin/staleness_checker.rb:146:in `dependencies'
  /usr/lib64/ruby/gems/1.9.1/gems/sass-3.2.0.alpha.244/lib/sass/plugin/staleness_checker.rb:123:in `dependencies_stale?'
  /usr/lib64/ruby/gems/1.9.1/gems/sass-3.2.0.alpha.244/lib/sass/plugin/staleness_checker.rb:161:in `block in dependency_updated?'
  /usr/lib64/ruby/gems/1.9.1/gems/sass-3.2.0.alpha.244/lib/sass/plugin/staleness_checker.rb:79:in `call'
  /usr/lib64/ruby/gems/1.9.1/gems/sass-3.2.0.alpha.244/lib/sass/plugin/staleness_checker.rb:79:in `stylesheet_modified_since?'
  /usr/lib64/ruby/gems/1.9.1/gems/sass-3.2.0.alpha.244/lib/sass/plugin/staleness_checker.rb:67:in `stylesheet_needs_update?'
  /usr/lib64/ruby/gems/1.9.1/gems/compass-0.13.alpha.0/lib/compass/compiler.rb:67:in `needs_update?'
  /usr/lib64/ruby/gems/1.9.1/gems/compass-0.13.alpha.0/lib/compass/compiler.rb:61:in `block in out_of_date?'
  /usr/lib64/ruby/gems/1.9.1/gems/compass-0.13.alpha.0/lib/compass/compiler.rb:60:in `each'
  /usr/lib64/ruby/gems/1.9.1/gems/compass-0.13.alpha.0/lib/compass/compiler.rb:60:in `out_of_date?'
  /usr/lib64/ruby/gems/1.9.1/gems/compass-0.13.alpha.0/lib/compass/commands/watch_project.rb:143:in `recompile'
  /usr/lib64/ruby/gems/1.9.1/gems/compass-0.13.alpha.0/lib/compass/commands/watch_project.rb:68:in `perform'
  /usr/lib64/ruby/gems/1.9.1/gems/compass-0.13.alpha.0/lib/compass/commands/base.rb:18:in `execute'
  /usr/lib64/ruby/gems/1.9.1/gems/compass-0.13.alpha.0/lib/compass/commands/project_base.rb:19:in `execute'
  /usr/lib64/ruby/gems/1.9.1/gems/compass-0.13.alpha.0/lib/compass/exec/sub_command_ui.rb:43:in `perform!'
  /usr/lib64/ruby/gems/1.9.1/gems/compass-0.13.alpha.0/lib/compass/exec/sub_command_ui.rb:15:in `run!'
  /usr/lib64/ruby/gems/1.9.1/gems/compass-0.13.alpha.0/bin/compass:29:in `block in <top (required)>'
  /usr/lib64/ruby/gems/1.9.1/gems/compass-0.13.alpha.0/bin/compass:43:in `call'
  /usr/lib64/ruby/gems/1.9.1/gems/compass-0.13.alpha.0/bin/compass:43:in `<top (required)>'
  /usr/bin/compass:19:in `load'
  /usr/bin/compass:19:in `<main>'

As discussed in IRC, I will do a little bit more debugging once I get permissions to do so on the server.

We want all files for sites to have the developers group and be group writable. umask can be used to set the default permissions. /etc/bashrc sets this to 002 for me, but 022 for snugug since our accounts are created differently. 002 is more correct, and will do the right thing for new files, like these. I'm not sure if it is best to edit /etc/bashrc directly, use puppet, or something else.

In the meantime, chmod -R g+w as needed.

Tagging for Sprint 5.

Drumm's advice to chmod -R g+w the .sass-cache directory allows us to run the compass watch command! Hooray!