Skip to content
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

Chmod files on EPERM on win32. #26

Merged
merged 1 commit into from
Jul 14, 2013
Merged

Chmod files on EPERM on win32. #26

merged 1 commit into from
Jul 14, 2013

Conversation

paulmillr
Copy link
Contributor

Superseeds gh-24.

@mdlawson
Copy link

Just tested this on windows. While no errors are thrown, nothing appears to have actually been deleted. Tested on the .git dir of a clone of this repo.

@paulmillr
Copy link
Contributor Author

Does sync version work?

@mdlawson
Copy link

Sync version somehow gets an EPERM in the same situation. There, I suspect
L135 is at fault, and needs an else. Didn't debug properly though.

@paulmillr
Copy link
Contributor Author

I’ve did live testing and investigation.

It is because windows throws EPERM for non-empty dirs on fs.unlink: nodejs/node-v0.x-archive#5791

Fixed this. Now works properly!

@isaacs @mdlawson

@isaacs isaacs merged commit 04b22e8 into isaacs:master Jul 14, 2013
@isaacs
Copy link
Owner

isaacs commented Jul 14, 2013

Merged this in, and then did a bit of code cleanup and published as 2.2.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants