Created attachment 618863 [details]
force_clean_build.log

Description of problem:
Create a php app, add force_clean_build marker and git push, caught error: "remote: no write access to /var/lib/stickshift/1dfbcad1b4cc4908a9a9237c997f5c6f/.pearrc!"

Version-Release number of selected component (if applicable):
On fork_ami_2105_189

How reproducible:
Always

Steps to Reproduce:
1. Create a php application
2. In app's local repo, add force_clean_build marker
touch .openshift/markers/force_clean_build
3. make some change in repo and git push
  
Actual results:
remote: Running .openshift/action_hooks/pre_build
remote: .openshift/markers/force_clean_build found!  Recreating pear libs
remote: 
remote: Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in Registry.php on line 1012
remote: PHP Warning:  date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /usr/share/pear/PEAR/Registry.php on line 1012
............
remote: no write access to /var/lib/stickshift/1dfbcad1b4cc4908a9a9237c997f5c6f/.pearrc!

Expected results:
force_clean_build should be successful.

Additional info:
Added output as attachement.