Home → Problems →

npm error, operation not permited on renaming a package.tgz

• Edit

Olivier Lefebvre

16 Sep, 2016 06:14 PM

Hi,

My build fail with this trace :

npm ERR! argv "C:\\Program Files (x86)\\nodejs\\node.exe" "C:\\Users\\appveyor\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install" "--force" "--quiet" "--depth" "0" "--progress" "false"
npm ERR! node v4.4.7
npm ERR! npm v3.10.7
npm ERR! path C:\Users\appveyor\AppData\Roaming\npm-cache\source-map\0.5.6\package.tgz.1141149376
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall rename
npm ERR! Error: EPERM: operation not permitted, rename 'C:\Users\appveyor\AppData\Roaming\npm-cache\source-map\0.5.6\package.tgz.1141149376' -> 'C:\Users\appveyor\AppData\Roaming\npm-cache\source-map\0.5.6\package.tgz'
npm ERR! at Error (native)
npm ERR! { [Error: EPERM: operation not permitted, rename 'C:\Users\appveyor\AppData\Roaming\npm-cache\source-map\0.5.6\package.tgz.1141149376' -> 'C:\Users\appveyor\AppData\Roaming\npm-cache\source-map\0.5.6\package.tgz']
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'rename',
npm ERR! path: 'C:\\Users\\appveyor\\AppData\\Roaming\\npm-cache\\source-map\\0.5.6\\package.tgz.1141149376',
npm ERR! dest: 'C:\\Users\\appveyor\\AppData\\Roaming\\npm-cache\\source-map\\0.5.6\\package.tgz',
npm ERR! parent: 'gulp-sourcemaps' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! Please include the following file with any support request:
npm ERR! C:\projects\chatle\src\chatle.aurelia\npm-debug.log

I tried to use --force option or not to use id, I tried to install the las npm, but nothing fix it.

The full log is there : https://ci.appveyor.com/project/aguacongas/chatle

Any idea ?

1. 1 Posted by Ilya Finkelshte... on 16 Sep, 2016 10:47 PM

   

   Hi Oliver,

   It looks like you use UI configuration in Appveyor. Could you please drop us your configuration in YAML format (use Export YAML menu).

   Thank you,
   Ilya.

   • Edit

2. 2 Posted by O. L. on 17 Sep, 2016 09:46 AM

   

   Hi Ilya,
   Thanks to reply, my appeveyor.yml is in attachment.
   Thank u

   Olivier Lefebvre+33 6 66 26 07 10follow me on twitterMy stackoverflow profile

   • appveyor.yml 2.28 KB
   • Edit

3. 3 Posted by Ilya Finkelshte... on 20 Sep, 2016 04:50 AM

   

   Hi Oliver,

   Sorry I misunderstood the problem initially, I should not ask you to send me YAML file.

   This EPEM error is very generic and usually related to some specific dependency. I opened your build log and It looks like this specific error does not happen anymore. Figure it out, or it is just stopped happening?

   Ilya.

   • Edit

4. 4 Posted by O. L. on 20 Sep, 2016 06:24 PM

   

   Hi ILya,
   It's still happening, look the last build https://ci.appveyor.com/project/aguacongas/chatle at line 953

   Olivier Lefebvre+33 6 66 26 07 10follow me on twitterMy stackoverflow profile

   • Edit

5. 5 Posted by Ilya Finkelshte... on 21 Sep, 2016 04:01 AM

   

   Hi Oliver,

   There are 2 approaches you can try:

   1. Move npm install from build to install stage. Thus all dependencies will be installed on VM before build which might eliminate the issue.

   2. Remove packages from package.json one by one and try to rebuild – thus you will find problem package. By the way I see 2 package.json files in your deployment (src\chatle.aurelia\package.json and chatle\src\chatle.aurelia\package.json) and I am not sure what is being used.

   Please let us know if this helps.

   --ilya.

   • Edit

6. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:08 AM.