Skip to content

during install, mkdir uc.micro failed on windows 7 #739

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ceced opened this issue May 12, 2016 · 2 comments
Closed

during install, mkdir uc.micro failed on windows 7 #739

ceced opened this issue May 12, 2016 · 2 comments

Comments

@ceced
Copy link

ceced commented May 12, 2016

Please provide us with the following information:

  1. OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Windows 7

  1. Versions. Please run ng --version. If there's nothing outputted, please
    run in a Terminal:
    node --version
    And paste the result here.

$ node --version
v4.4.4

  1. Repro steps. Was this an app that wasn't created using the CLI? What change did you
    do on your code? etc.

npm install -g angular-cli

  1. The log given by the failure. Normally this include a stack trace and some
    more information.

140520 info install bower@1.7.9
140521 info postinstall bower@1.7.9
140522 verbose unlock done using C:\Users\m346221\AppData\Roaming\npm-cache_locks\bower-e9a25357a51bcd3d.lock for C:\workspaces\angular\node_modules\angular-cli\node_modules\ember-cli\node_modules\bower
140523 verbose about to build C:\workspaces\angular\node_modules\angular-cli\node_modules\ember-cli
140524 verbose unlock done using C:\Users\m346221\AppData\Roaming\npm-cache_locks\ember-cli-333e4f52b94c615e.lock for C:\workspaces\angular\node_modules\angular-cli\node_modules\ember-cli
140525 verbose about to build C:\workspaces\angular\node_modules\angular-cli
140526 verbose unlock done using C:\Users\m346221\AppData\Roaming\npm-cache_locks\angular-cli-24f02dc10fa0be9b.lock for C:\workspaces\angular\node_modules\angular-cli
140527 verbose stack Error: EPERM: operation not permitted, mkdir 'C:\Users\m346221\AppData\Local\Temp\npm-612-1c760466\registry.npmjs.org\uc.micro'
140527 verbose stack at Error (native)
140528 verbose cwd C:\workspaces\angular
140529 error Windows_NT 6.1.7601
140530 error argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "angular-cli"
140531 error node v4.4.4
140532 error npm v2.15.1
140533 error path C:\Users\m346221\AppData\Local\Temp\npm-612-1c760466\registry.npmjs.org\uc.micro
140534 error code EPERM
140535 error errno -4048
140536 error syscall mkdir
140537 error Error: EPERM: operation not permitted, mkdir 'C:\Users\m346221\AppData\Local\Temp\npm-612-1c760466\registry.npmjs.org\uc.micro'
140537 error at Error (native)
140537 error { [Error: EPERM: operation not permitted, mkdir 'C:\Users\m346221\AppData\Local\Temp\npm-612-1c760466\registry.npmjs.org\uc.micro']
140537 error errno: -4048,
140537 error code: 'EPERM',
140537 error syscall: 'mkdir',
140537 error path: 'C:\Users\m346221\AppData\Local\Temp\npm-612-1c760466\registry.npmjs.org\uc.micro',
140537 error parent: 'markdown-it' }
140538 error Please try running this command again as root/Administrator.
140539 verbose exit [ -4048, true ]

  1. Mention any other details that might be useful.

tried with windows command line with admin rights ( but cannot bypass corporate gpo ), and without admin rights.
tried with git bash ( mingw32 ) with admin rights ( but cannot bypass corporate gpo ), and without admin rights.
Same results ...

It seems we cannot create a dir called something.micro on windows 7 ?
Strange...
Thank you for your help !


Thanks! We'll be in touch soon.

@ceced ceced changed the title mkdir uc.micro failed on windows 7 during install, mkdir uc.micro failed on windows 7 May 12, 2016
@hansl
Copy link
Contributor

hansl commented May 13, 2016

Hi, try with Node 5. It might solve your problem.

Otherwise, I'm not sure what can be done here.

@hansl hansl closed this as completed May 13, 2016
clydin pushed a commit that referenced this issue Jun 5, 2018
…e.json

In a6767dc, a defaultProject was added to workspaceJson in workspace_spec, which hasn't been
synced with tests/@angular_devkit/workspace/angular-workspace.json as expected. This was breaking
the related tests with more than one project, like in #739.
hansl pushed a commit that referenced this issue Jun 6, 2018
…e.json

In a6767dc, a defaultProject was added to workspaceJson in workspace_spec, which hasn't been
synced with tests/@angular_devkit/workspace/angular-workspace.json as expected. This was breaking
the related tests with more than one project, like in #739.
hansl pushed a commit that referenced this issue Jun 6, 2018
…e.json

In a6767dc, a defaultProject was added to workspaceJson in workspace_spec, which hasn't been
synced with tests/@angular_devkit/workspace/angular-workspace.json as expected. This was breaking
the related tests with more than one project, like in #739.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants