On Tue, Mar 20, 2012 at 1:13 PM, Keshav Kini <keshav.k...@gmail.com> wrote: > John Cremona <john.crem...@gmail.com> writes: >> Indeed: every time I build my working copy of Sage (not counting test >> version here) I have to do first sage -i openssl and then sage -f >> python to rebuild python. Otherwise some mercurial stuff does not >> work (complains of not having _ssl, I think). The sort of thing which >> does not work is pull/push requests froma remote repository. > > The git spkg I just made is unable to communicate with repositories over > HTTP (unless you just happen to have libcurl and libexpat installed > systemwide - I didn't want to package them since libcurl's source code > is almost as large again as git's; I didn't look at libexpat). > > Would this be a problem for you once we switch to git? What do you use > Sage's Mercurial for which requires pushing and pulling to/from a remote > repository?
He uses http://code.google.com/p/lmfdb/issues/list and http://code.google.com/p/purplesage/ which both *require* https for pushing (though not for pulling if you url hack). William > > -Keshav > > ---- > Join us in #sagemath on irc.freenode.net ! > > -- > To post to this group, send an email to sage-devel@googlegroups.com > To unsubscribe from this group, send an email to > sage-devel+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org -- William Stein Professor of Mathematics University of Washington http://wstein.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org