-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
currently uninstallable on 0.6.2. #187
Comments
Thanks for reporting! I'll look into this tomorrow unless someone beats me to it |
This sometimes happens when packages aren't precompiled before loading a dependent package Could you please try |
happy to do so. (PS: I do not need this right now. I am just trying to help. I presume by 1.0 with a new package manager, the stability will return.)
|
Let me add that I had wiped ~/.julia/v0.6, and then proceeded to reinstall everything as follows:
Unless the package installer is even more flaky than I think it is, this should reproduce the problem in case anyone is interested. |
@iwelch thanks for being willing to help! Yes, I think stability will be much easier for package authors/maintainers to achieve once 1.0 is out -- in large part because of the new package manager like you mentioned. Can you describe your setup a bit more? Which OS are you using? Which front end are you using to julia: command line version, jupyter notebook, juno? Our tests are able to run on 0.6.2 on Linux and command line julia -- which includes the installation step, so I'm not sure exactly why this would be happening with your setup |
OS: macOS. latest version.
command line. (the error happens on two choices to try to replicate---[1] just ignore (its unimportant to me, too). [2] rm -rf the julia v0.6 contents, then run my long pkg.add / using list above. see if it replicates. takes a while, though. regards, /iaw |
come to think of it, wait until I do it from scratch again. I will report back if I can recreate it on the same machine from scratch, first. if not, it was a package manager hiccup somewhere?! |
full reinstall. bug is gone now. lovely. so, ignore. |
Thanks for following up |
The text was updated successfully, but these errors were encountered: