Hi Isaiah, just tried that but didnt work. it's again:
error: SSL certificate problem, verify that the CA cert is OK. so this may be a problem with my system. thanks for checking back! I'll post any followups here. On 30 July 2014 22:47, Isaiah Norton <[email protected]> wrote: > I believe the following should work, provided you have github ssh keys > configured (which seems to be the case): > > git config --global url."ssh://".insteadOf git:// > > If you have a chance to test the above and it works, then we could add it > as another suggestion to the README (especially for hpc and similar > environments with tricky network configs). Temporarily renaming your > ~/.julia folder is a safe way to do such a test. > > > > On Wed, Jul 30, 2014 at 5:01 PM, Florian Oswald <[email protected]> > wrote: > >> Very helpful, thanks! >> I resorted to manually cloning all my packages, completely bypassing the >> package manager. That takes a while but it works. >> I tried hard to get this ssl thing going but it's difficult on a large >> hpc system. I'll go on begging the sys admins. >> >> >> On Wednesday, 30 July 2014, Isaiah Norton <[email protected]> >> wrote: >> >>> Ok, I see. The difference is that the first and third URLs (with the >>> colon after the domain name) are scp-style addresses, so git uses SSH to >>> connect [1]. At least for METADATA initialization, you can do this: >>> >>> Pkg.init("github.com:JuliaLang/METADATA.jl") >>>> >>> >>> However, I'm not sure what will happen when cloning packages. Perhaps >>> some `insteadOf` rules can help. >>> >>> Regarding the original error, google suggests it may be due to a >>> poorly-configured proxy, or missing CA certs. Stackoverflow has a large >>> number of suggestions for possible solutions [2] >>> >>> [1] https://www.kernel.org/pub/software/scm/git/docs/git-push.html#URLS >>> [2] >>> http://stackoverflow.com/questions/3777075/ssl-certificate-rejected-trying-to-access-github-over-https-behind-firewall >>> >>> >>> On Wed, Jul 30, 2014 at 1:47 PM, Florian Oswald < >>> [email protected]> wrote: >>> >>>> that didnt' work: >>>> >>>> git config --global url."https://".insteadOf git:// >>>> notice that i don't just want to have https:// instead of git:// (both >>>> don't work). i need a different call altogether, see below. >>>> >>>> >>>> On 30 July 2014 18:36, Isaiah Norton <[email protected]> wrote: >>>> >>>>> yes - search for "insteadOf" or "https" in the readme. >>>>> >>>>> >>>>> On Wed, Jul 30, 2014 at 1:11 PM, Florian Oswald < >>>>> [email protected]> wrote: >>>>> >>>>>> hmm, I don't know. but - this works: >>>>>> >>>>>> git clone [email protected]:tlamadon/Utils.git >>>>>> >>>>>> and this does not >>>>>> >>>>>> git clone git://github.com/JuliaLang/METADATA.jl >>>>>> >>>>>> but that does >>>>>> >>>>>> git clone [email protected]:JuliaLang/METADATA.jl >>>>>> >>>>>> I see. is there a way to tell julia to use the latter version? >>>>>> >>>>>> >>>>>> >>>>>> On Wednesday, 30 July 2014 18:06:03 UTC+1, Ivar Nesje wrote: >>>>>>> >>>>>>> Do you clone the other repositories over https or the ssh based git >>>>>>> protocol? >>>>>>> >>>>>>> kl. 19:03:06 UTC+2 onsdag 30. juli 2014 skrev Florian Oswald >>>>>>> følgende: >>>>>>>> >>>>>>>> i'm working on a remote server that has >>>>>>>> >>>>>>>> git version 1.7.4.1 >>>>>>>> >>>>>>>> I could use this git to build julia and clone a host of other >>>>>>>> repos, but when I want to do >>>>>>>> >>>>>>>> Pkg.status() >>>>>>>> >>>>>>>> it fails with >>>>>>>> >>>>>>>> error: SSL certificate problem, verify that the CA cert is OK. >>>>>>>> Details: >>>>>>>> >>>>>>>> error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate >>>>>>>> verify failed while accessing https://github.com/JuliaLang/ >>>>>>>> METADATA.jl/info/refs >>>>>>>> >>>>>>>> is there anything special about the METADATA repo? is my git out of >>>>>>>> date? >>>>>>>> >>>>>>>> thanks. >>>>>>>> >>>>>>>> >>>>>>>> >>>>> >>>> >>> >
