Check Pkg.status(). Most likely, a package that you actually did add has changed its dependencies with its latest version.
To prevent this (or at least make the error more obviously visible) you should be able to create a directory or file or something to get in the way in your personal copy of METADATA to "reserve" the names of your private packages, then the first Pkg.update() you run after a public package with that name gets registered you should see git complain. On Thursday, June 16, 2016 at 12:28:41 PM UTC-7, Eric Forgy wrote: > > Hi, > > I have a private package "A.jl" and it turns out there is also a public > package "A.jl" I didn't know about. I manually moved my package folder from > my package directory to another folder, updated LOAD_PATH so everything > still worked and did a Pkg.update(). For some reason, Pkg.update() then > pulled down the public "A.jl" causing the public "A.jl" to take precedence > over my private "A.jl". > > It took me some time to figure out why my code was no longer working. > > Why did Pkg.update() pull down a public package that I never Pkg.add()'ed? > > What should I do to avoid this in the future? > > Thanks, > Eric > > julia> versioninfo() > Julia Version 0.4.5 > Commit 2ac304d (2016-03-18 00:58 UTC) > Platform Info: > System: Windows (x86_64-w64-mingw32) > CPU: Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz > WORD_SIZE: 64 > BLAS: libopenblas (USE64BITINT DYNAMIC_ARCH NO_AFFINITY Haswell) > LAPACK: libopenblas64_ > LIBM: libopenlibm > LLVM: libLLVM-3.3 > > >
