Ah, I see. On one hand that makes sense. On the other hand, I’ve been under the impression for more than two years now that if I remove a package via Pkg.rm and it doesn’t show up in Pkg.status, it is no longer on my disc. Doesn’t seem an unreasonable expectation, so maybe that is something to clarify somewhere.
From: [email protected] [mailto:[email protected]] On Behalf Of Stefan Karpinski Sent: Tuesday, June 21, 2016 11:29 AM To: Julia Users <[email protected]> Subject: Re: [julia-users] Re: Git-maggedon Yes, that's right. The cache is also shared between different Julia versions. On Tue, Jun 21, 2016 at 1:49 PM, David Anthoff <[email protected] <mailto:[email protected]> > wrote: You mean when I completely uninstalled a package and then add it again? It wouldn’t be needed if I just switch to a different version of an installed package, right? From: <mailto:[email protected]> [email protected] [mailto: <mailto:[email protected]> [email protected]] On Behalf Of Stefan Karpinski Sent: Tuesday, June 21, 2016 10:45 AM To: Julia Users < <mailto:[email protected]> [email protected]> Subject: Re: [julia-users] Re: Git-maggedon The cache folders are just bare git repositories for packages. Keeping these around prevents having to hit the network to reinstall a package version that you've already fetched and installed before. On Tue, Jun 21, 2016 at 1:31 PM, David Anthoff <[email protected] <mailto:[email protected]> > wrote: I’ve never understood the various .cache folders that hang around, but if you want to be sure to start from a clean .julia package folder you might want to make sure all the .cache folders are also removed. In particular I guess the .julia/.cache folder. And then retry the whole Pkg.init() procedure. From: <mailto:[email protected]> [email protected] [mailto: <mailto:[email protected]> [email protected]] On Behalf Of Eric Forgy Sent: Tuesday, June 21, 2016 10:24 AM To: julia-users < <mailto:[email protected]> [email protected]> Subject: [julia-users] Re: Git-maggedon Update: I went back and changed v0.4 -> v0.4_temp2 and did a Pkg.Init() and Pkg.add("JSON") using v0.4.5 just to see if it was related to upgrading. I see the exact same problem. I suspect my Git is corrupted somehow which is wreaking havoc with Pkg. That is just a guess. Any ideas? On Wednesday, June 22, 2016 at 12:37:50 AM UTC+8, Eric Forgy wrote: I just upgraded to v0.4.6 on Windows, but I think this problem might predate the upgrade (I think the upgrade was partially in hopes of resolving this). I don't know if this is a Julia issue or a Git issue, but if I add any package, e.g. julia> Pkg.add("JSON") The package gets added to my package directory, but no branch is checked out so I am on HEAD. Worse, instead of my remotes being things like: remotes/origin/master I see things like remotes/cached/heads/master Any idea what's going on? I'm on a critical business trip and my development is completely paralyzed until I can resolve this so I really sincerely appreciate any help. In an act of desperation, I moved v0.4 -> v0.4_temp, Pkg.init() and reinstalled every single package. I still have exactly the same problem, so I am unable to do anything with Julia until I fix this. Thank you very much and best regards, Eric
