-
Notifications
You must be signed in to change notification settings - Fork 372
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
opam caused a significant portion of my home directory to be deleted #3231
Comments
Okay, this seems to have been the issue: camlp5/camlp5#18 Edit: The dependency might be updated now? I'm not sure how to double-check. It's possible I was using a version that missed the fix by a day or so. |
I am very sorry for this outcome, and feel for you. I am hoping you had backups or online versions of any valuable files 😢 opam will only run commands within Again, I am very sorry this happened to you 😞 ¹ We do have optional sandboxing, but it is still being tested and needs some manual configuration. The upcoming pam 2 can also automatically take care of package uninstallation. |
Indeed, it seems it had been fixed. opam doesn't auto-update, unfortunately, so without running |
Seems like a case of very unfortunate bad timing. It seems also like there will be mitigations to prevent this sort of thing happening in opam in the future, so I think there's nothing more to be said here. Thanks for looking into it! |
Every file owned by my user account is gone from my system (~400G of data). I can open another ticket if need be. @AltGr @varkor It seems opam will update/upgrade if you compiler version changes. I upgraded ocaml from 4.06.0 to 4.06.1 and it nuked my home directory. I am sad.
|
oh noh! I can't express how sorry I am about this. |
It's not entirely clear exactly what happened, as most of my files have been lost, and my programs corrupted, but I have the log from right before the problem occurred:
I'm fairly sure it was executing
make uninstall camlp5
before I killed it after noticing that it was taking an unexpected amount of time (so maybe the problem is there), though I think the issue is relevant here regardless.I'm still a little in shock at having ruined my computer at the moment, so I may try to look into this a little more later, but I think this issue definitely needs to be looked into.
The text was updated successfully, but these errors were encountered: