# Add package, but the following error was reported, how to solve it, thank you
**URL:** https://discourse.julialang.org/t/add-package-but-the-following-error-was-reported-how-to-solve-it-thank-you/96112
**Category:** General Usage
**Tags:** question, pkg, registry
**Created:** [March 15, 2023, 9:04am UTC](https://discourse.julialang.org/t/add-package-but-the-following-error-was-reported-how-to-solve-it-thank-you/96112 "2023-03-15T09:04:41Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Yanjj1](https://discourse.julialang.org/u/Yanjj1)
#### Post date: [March 15, 2023, 9:04am UTC](https://discourse.julialang.org/t/add-package-but-the-following-error-was-reported-how-to-solve-it-thank-you/96112/1 "2023-03-15T09:04:41Z")
(@v1.7) pkg\> add GLM
Updating registry at ~/.julia/registries/General
ERROR: GitError(Code:ENOTFOUND, Class:Repository, could not find repository from ‘/public/user/.julia/registries/General’)
Stacktrace:
[1] macro expansion
@ ~/packages/julias/julia-1.7/share/julia/stdlib/v1.7/LibGit2/src/error.jl:110 [inlined]
[2] LibGit2.GitRepo(path::String)
@ LibGit2 ~/packages/julias/julia-1.7/share/julia/stdlib/v1.7/LibGit2/src/repository.jl:11
[3] update(regs::Vector{Pkg.Registry.RegistrySpec}; io::Base.TTY, force::Bool)
@ Pkg.Registry ~/packages/julias/julia-1.7/share/julia/stdlib/v1.7/Pkg/src/Registry/Registry.jl:403
[4] update\_registries(ctx::Pkg.Types.Context; force::Bool, kwargs::Base.Pairs{Symbol, Union{}, Tuple{}, NamedTuple{(), Tuple{}}})
@ Pkg.Operations ~/packages/julias/julia-1.7/share/julia/stdlib/v1.7/Pkg/src/Operations.jl:1072
[5] add(ctx::Pkg.Types.Context, pkgs::Vector{Pkg.Types.PackageSpec}; preserve::Pkg.Types.PreserveLevel, platform::Base.BinaryPlatforms.Platform, kwargs::Base.Pairs{Symbol, Base.TTY, Tuple{Symbol}, NamedTuple{(:io,), Tuple{Base.TTY}}})
@ Pkg.API ~/packages/julias/julia-1.7/share/julia/stdlib/v1.7/Pkg/src/API.jl:252
[6] add(pkgs::Vector{Pkg.Types.PackageSpec}; io::Base.TTY, kwargs::Base.Pairs{Symbol, Union{}, Tuple{}, NamedTuple{(), Tuple{}}})
@ Pkg.API ~/packages/julias/julia-1.7/share/julia/stdlib/v1.7/Pkg/src/API.jl:149
[7] add(pkgs::Vector{Pkg.Types.PackageSpec})
@ Pkg.API ~/packages/julias/julia-1.7/share/julia/stdlib/v1.7/Pkg/src/API.jl:144
[8] do\_cmd!(command::Pkg.REPLMode.Command, repl::REPL.LineEditREPL)
@ Pkg.REPLMode ~/packages/julias/julia-1.7/share/julia/stdlib/v1.7/Pkg/src/REPLMode/REPLMode.jl:407
[9] do\_cmd(repl::REPL.LineEditREPL, input::String; do\_rethrow::Bool)
@ Pkg.REPLMode ~/packages/julias/julia-1.7/share/julia/stdlib/v1.7/Pkg/src/REPLMode/REPLMode.jl:385
[10] do\_cmd
@ ~/packages/julias/julia-1.7/share/julia/stdlib/v1.7/Pkg/src/REPLMode/REPLMode.jl:376 [inlined]
[11] (::Pkg.REPLMode.var"#24#27"{REPL.LineEditREPL, REPL.LineEdit.Prompt})(s::REPL.LineEdit.MIState, buf::IOBuffer, ok::Bool)
@ Pkg.REPLMode ~/packages/julias/julia-1.7/share/julia/stdlib/v1.7/Pkg/src/REPLMode/REPLMode.jl:549
[12] #invokelatest#2
@ ./essentials.jl:716 [inlined]
[13] invokelatest
@ ./essentials.jl:714 [inlined]
[14] run\_interface(terminal::REPL.Terminals.TextTerminal, m::REPL.LineEdit.ModalInterface, s::REPL.LineEdit.MIState)
@ REPL.LineEdit ~/packages/julias/julia-1.7/share/julia/stdlib/v1.7/REPL/src/LineEdit.jl:2493
[15] run\_frontend(repl::REPL.LineEditREPL, backend::REPL.REPLBackendRef)
@ REPL ~/packages/julias/julia-1.7/share/julia/stdlib/v1.7/REPL/src/REPL.jl:1230
[16] (::REPL.var"#49#54"{REPL.LineEditREPL, REPL.REPLBackendRef})()
@ REPL ./task.jl:423
---
### Author:  [@mkitti](https://discourse.julialang.org/u/mkitti)
#### Post date: [March 15, 2023, 9:26am UTC](https://discourse.julialang.org/t/add-package-but-the-following-error-was-reported-how-to-solve-it-thank-you/96112/2 "2023-03-15T09:26:53Z")
I’m confused but you might want to try
```julia
using Pkg
pkg"registry rm"
pkg"registry add"
```
---
### Author:  [@Yanjj1](https://discourse.julialang.org/u/Yanjj1)
#### Post date: [March 15, 2023, 11:52am UTC](https://discourse.julialang.org/t/add-package-but-the-following-error-was-reported-how-to-solve-it-thank-you/96112/3 "2023-03-15T11:52:38Z")
This method is effective and has been solved, thank you