Results 1 to 2 of 2

Thread: sencha app build with read-only files = [ERROR] EPERM, operation not permitted

    Success! Looks like we've fixed this one. According to our records the fix was applied for TOUCH-2860 in a recent build.
  1. #1
    Sencha User
    Join Date
    Mar 2011
    Vote Rating

    Default sencha app build with read-only files = [ERROR] EPERM, operation not permitted

    Hello Sencha team,

    my directory with the Sencha Touch application is under the TFS source control (Windows 7, 64-bit). That means all files that are not checked out are marked as read-only. When building an application with `sencha app build production` command, the application is built only for the first time. After that, any other attempt to build the application results in `[ERROR] EPERM, operation not permitted`. The reason is that the files were copied with the read-only flag and cannot now be overwritten.

    Currently, I am deleting those files manually, but I think it would be better to copy the files without the read-only flag.

  2. #2
    Sencha - Sr Software Engineer mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Gainesville, FL
    Vote Rating


    Thanks for the report. You could create a bat file to do the build for you doing the deleting first and then executing the sencha app build
    Mitchell Simoens @LikelyMitch
    Sencha Inc, Senior Software Engineer
    Learn BBCode and use it!

    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2

    Think my support is good? Get more personalized support via a support subscription.

    Need more help with your app? Hire Sencha Services

    Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!

    When posting code, please use BBCode's CODE tags.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts