I'm not sure. When you run in git-bash, is the environment variable HOME set? If you set it in Julia, does it change anything?
On Wednesday, October 14, 2015 at 2:10:48 AM UTC-7, Tomas Lycken wrote: > > Thanks! That was a useful pointer, and it got me someways down the road, > but I still see really weird things... > > Without me (knowingly) changing anything, I went into the Julia install > folder, into Git, and double-clicked git-bash.cmd. That opened a bash > shell, in which I could cd to e.g. the METADATA.jl package directory and do > git pull. It asked me to accept the server's fingerprint, but otherwise > didn't complain. git pull worked then without error. > > After doing this, I started a new Julia 0.4.0 instance, and now > Pkg.update() works - once. The second time, it borked on a couple of > repositories which I have forked, but where my fork is not the "main > source", with the message "error: could not fetch tlycken" (which is the > name of my fork in the output of `git remote -v`; I still have a remote > called origin). Manually going into those package directories using > git-bash, and manually saying `git fetch tlycken`, completes without error. > > If Julia is using the same git as the git-bash from Julia's installation > folder, why can one fetch without problem, while the other is denied > permission? > > // T > > > On Wednesday, October 14, 2015 at 10:34:00 AM UTC+2, Tony Kelman wrote: >> >> The Win and Mac binaries bundle their own git, rather than relying on >> having it manually installed and on the path. Check the Git folder under >> the Julia install, run the git-bash there to try getting keys working. > >
