# Julia 1.4 can't update registry

**URL:** <https://discourse.julialang.org/t/julia-1-4-cant-update-registry/36390>\
**Category:** General Usage\
**Created:** [March 23, 2020, 12:45pm UTC](https://discourse.julialang.org/t/julia-1-4-cant-update-registry/36390 "2020-03-23T12:45:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pixel27](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pixel27/32/8902_2.png) [@pixel27](https://discourse.julialang.org/u/pixel27)\
**Post date:** [March 23, 2020, 12:45pm UTC](https://discourse.julialang.org/t/julia-1-4-cant-update-registry/36390/1 "2020-03-23T12:45:39Z")

</div>

I have a VM running Manjaro on the test branch. I wanted to check if Julia 1.4 made has made it onto the test branch so I fired up the VM updated it and yes 1.4 has made it into test.

So I wanted to test it. I hadn’t installed Juno in Atom, so I figured I’d do that first. Added uber-juno to Atom. Started Julia in the tray…and “Outdated version of Atom.jl” (0.12.7)…okay weird, I just installed it, why the old version. Tried to update, didn’t update.

Found an **old** post about the registry being dirty, figured I’d try that…didn’t help…ended up with a different error. Okay, start over, deleted `~/.julia`. Now I just can’t update.

```julia
               _
   _ _ _(_)_ | Documentation: https://docs.julialang.org
  (_) | (_) (_) |
   _ _ _| |_ __ _ | Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` | |
  | | |_| | | | (_| | | Version 1.4.0 (2020-03-21)
 _/ |\ __'_|_|_|\__'_| |  
|__/ |

(@v1.4) pkg> update
    Cloning default registries into `~/.julia`
    Cloning registry from "https://github.com/JuliaRegistries/General.git"
ERROR: failed to clone from https://github.com/JuliaRegistries/General.git, error: GitError(Code:ERROR, Class:Invalid, invalid version 0 on git_proxy_options)

```

I can open `https://github.com/JuliaRegistries/General.git` in a browser just fine…Not sure what is going on.

Some more information…When I start under Atom with `~/.julia` deleted I get:

```julia
Hold on tight while we are installing some packages for you.
This should only take a few seconds...

 Activating environment at `~/.julia/environments/v1.4/Project.toml`
    Cloning default registries into `~/.julia`
    Cloning registry from "https://github.com/JuliaRegistries/General.git"
ERROR: LoadError: failed to clone from https://github.com/JuliaRegistries/General.git, error: GitError(Code:ERROR, Class:Invalid, invalid version 0 on git_proxy_options)
Stacktrace:
 [1] top-level scope at /home/pixel/.atom/packages/julia-client/script/boot_repl.jl:21
in expression starting at /home/pixel/.atom/packages/julia-client/script/boot_repl.jl:1
caused by [exception 1]
GitError(Code:ERROR, Class:Invalid, invalid version 0 on git_proxy_options)
Stacktrace:
 [1] top-level scope at /home/pixel/.atom/packages/julia-client/script/boot_repl.jl:21
               _
   _ _ _(_)_ | Documentation: https://docs.julialang.org
  (_) | (_) (_) |
   _ _ _| |_ __ _ | Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` | |
  | | |_| | | | (_| | | Version 1.4.0 (2020-03-21)
 _/ |\ __'_|_|_|\__'_| |  
|__/ |

julia> 

```

However when I look in that directory it only has a logs folder with 2 empty files (manifest\_usage.toml and repl\_history.jl)…there is no “environments” directory.

Not sure if this is the distro’s issue or 1.4…

---

<div class="post-metadata">

**Author:** ![fredrikekre](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fredrikekre/32/1688_2.png) [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)\
**Post date:** [March 23, 2020, 1:26pm UTC](https://discourse.julialang.org/t/julia-1-4-cant-update-registry/36390/2 "2020-03-23T13:26:48Z")

</div>

Looks like you are not using the official binaries, so then I am guessing you have libgit version 0.99 and running into [Bug: compatibility with http-parser 2.9.3 and libgit2 0.99.0-2 · Issue #35043 · JuliaLang/julia · GitHub](https://github.com/JuliaLang/julia/issues/35043#issue-577431718). Other users report that downgrading libgit2 solves your problem.