In theory, point release upgrades (e.g. v1.0.0 → v1.0.2) contain bug fixes only and should be backwards compatible. They should be considered as a drop-in replacement. No need for multiple installations.
Oh I see, that is good to know. I will have to copy and paste my packages before deleting Julia 1.0.0 I assume.
No, just install new version of Julia v1.0.2, check everything works OK, then delete Julia v1.0.0. Packages should be unaffected.
1 Like
I am looking at this right now. Indeed, everything seems to be identical. Thank you both for your fast replies! 
I had the same exact issue. Removed the General folder with Windows Explorer and then followed with an “up” command in the REPL. All is good!
This worked for me too.
These solutions don’t work for me on ARMv7, 32-bit - even going into the General repo and git reset --hard HEAD don’t solve it. It appears that every file has been changed.
Edit: This seems to be a different problem; the error is introduced when a stdlib is added.
@fredrikekre, I read your posting and removed ~/.julia/registries/General/ directory without backing it up. In my case, restarting REPL followed by Pkg.update() did not recreate the directory.
(v1.4) pkg> update
Cloning default registries into `~/.julia`
Cloning registry from "https://github.com/JuliaRegistries/General.git"
ERROR: Git repository not found at 'https://github.com/JuliaRegistries/General.git'
If someone wants to try the suggestion in this posting, I recommend backing up the ~/.julia/registries/General/ directory before deleting.
EDIT. Maybe related with the Julia version. It does not work in version 1.4, but it works in version 1.0.
Works for me, you are probably running into https://github.com/JuliaLang/julia/issues/33111 (https://github.com/libgit2/libgit2/issues/5220, https://github.com/libgit2/libgit2/issues/5255)
From my case in Window 8.1/Julia v1.2, it was caused by “Stage Changed” that I switch the default package source address into mirror one without commit this change in Git. Assume you had installed Git in your PC, try to use Git bash or Git GUI to check it out. Once you commit the change, the error could be fixed.
Hope it could help.
