-
Notifications
You must be signed in to change notification settings - Fork 2
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
[1.2.0][Win10][VirtualBox] #38
Comments
The logic is pretty simple (source code):
That removes the ReadOnly attribute from files before deleting them. It does not add anything that was not there already. I can actually skip over the setting of the attributes if it fails. I am very very curious though what is special about your drive. I'm already preparing a prerelease for you ... I will add the skip of attributes. Can you wait on this a day while it gets tested? |
You are so nice ! Sorry for the imprecise reports ; I have not actually used Windows since ~2008 and WinXP and was not even a "power user" back then, so I do not really know was is going on in there. The drive is a virtualbox VDI. That it fails (and whith such a message) on removing an attribute is really strange. This is not an urgent matter at all. I have a working 4.14.0 from fdopen ; I am trying Diskuv out of curiosity and to see if I can get a working 5.0.0 OCaml (this because there happen to be some bug in 4.14.0 that affects backtraces on exceptions ; but this is not an urgent problem as I will only be doing pure functional programming for a while — pun not intended —, and the only exception I can think of in that context is a Failure due to a partial match, and they are obvious to spot). |
A fix for this is available at https://github.com/diskuv/dkml-installer-ocaml/releases/tag/v1.2.1-prerel1 |
Thank you so much ! I finally had some time to check this out, and indeed, opam installation works flawlessly with this build. |
At step 10, I get an error. Presumably I do not have some extended attribute thing installed — it would be nice to check for that at the beginning of the procedure.
The text was updated successfully, but these errors were encountered: