-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Can't delete read-only files on Windows #7573
Comments
Ah so that's what that was, good catch and apologies to @jakebolewski for my wrong guess in https://github.com/jakebolewski/LibGit2.jl/pull/11. Judging by Linux behavior here, I think we should only do a force removal of anything read-only via a new |
libgit object files are read-only by default. Objects like those Our linux behavior removes read-only files by default:
EDIT: Oh, this is OSX, not linux, but I would be surprised if Linux doesn't do this, as the LibGit2.jl tests have no problem with this kind of operation. |
Oh, so it does. Here I was assuming Julia's |
Yeah, |
I believe I fixed this in #7590 |
By default, windows balks at
rm
'ing files that have the read-only attribute set. This is causing theLibGit2.jl
tests to fail on Windows. My favorite solution is to ignore read-only files inside of libuv when removing files on windows. This might involve justchmod
'ing them before callingunlink
or something, but @jakebolewski and I wanted to run it past the rest of you to see what you thought; is there a better way to do this?The text was updated successfully, but these errors were encountered: