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
    Posts
    17
    Vote Rating
    0
      0  

    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 User mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    40,050
    Vote Rating
    1381
      0  

    Default

    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
    Modus Create, Senior Frontend Engineer
    ________________
    Need any sort of Ext JS help? Modus Create is here to help!

    Check out my GitHub:
    https://github.com/mitchellsimoens

Posting Permissions

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