stefanpenner/ember-app-kit

bower install failed on windows

Closed this issue · 2 comments

The bower install command is failing on windows. I did try using the command

bower cache clean

Here is the error I see in the console

bower jquery#>= 1.7.0 <= 2.1.0               extract archive.tar.gz
bower jquery#>= 1.7.0 <= 2.1.0              resolved git://github.com/jquery/jquery.git#2.1.0
bower ember#^1.3.0                             EPERM EPERM, unlink 'C:\Users\blessenm\AppData\Local\Temp\blessenm-PC-blessenm\bower\ember-2300-HN9ToM\archive.tar.gz'

Stack trace:
Error: EPERM, unlink 'C:\Users\blessenm\AppData\Local\Temp\blessenm-PC-blessenm\bower\ember-2300-HN9ToM\archive.tar.gz'

Console trace:
Trace
at StandardRenderer.error (C:\Users\blessenm\AppData\Roaming\npm\node_modules\bower\lib\renderers\StandardRenderer.js:74:17)
at Logger.<anonymous> (C:\Users\blessenm\AppData\Roaming\npm\node_modules\bower\bin\bower:114:22)
at Logger.EventEmitter.emit (events.js:95:17)
at Logger.emit (C:\Users\blessenm\AppData\Roaming\npm\node_modules\bower\node_modules\bower-logger\lib\Logger.js:29:39)
at C:\Users\blessenm\AppData\Roaming\npm\node_modules\bower\lib\commands\install.js:35:16
at _rejected (C:\Users\blessenm\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:797:24)
at C:\Users\blessenm\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:823:30
at Promise.when (C:\Users\blessenm\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:1035:31)
at Promise.promise.promiseDispatch (C:\Users\blessenm\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:741:41)
at C:\Users\blessenm\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:557:44

System info:
Bower version: 1.3.2
Node version: 0.10.26
OS: Windows_NT 6.1.7600 x64

@Blessenm what is the output of bower cache clean? Seems to be a bower permissions problem. Is the folder C:\Users\blessenm\AppData\Local\Temp\blessenm-PC-blessenm\bower\ember-2300-HN9ToM present? If so can you delete it and try again?

this issue should be opened on bower. feel free to report back any work arounds