The same working package is now uploading to the stable PPA. It is already in the dev PPA. We will probably next week turn on weekly autouploads to the dev PPA. And then release whenever there is a new sage and it is ready, to the stable PPA.
Regards, Jan On 23 September 2015 at 17:41, Jan Groenewald <j...@aims.ac.za> wrote: > Hi > > I think that it now works because our latest PPA package includes all the > build/bin folder in /usr/lib/sagemath. > Then when you have libssl-dev installed and do sudo sage -f python it is > installed with ssl. I'm guessing though. > > Regards, > Jan > > On 23 September 2015 at 17:00, Henri Girard <henri.gir...@gmail.com> > wrote: > >> In fact we must obtain (sagemanifolds and I... maybe more...(I guess but >> i don't want to speak in name of Eric) the following : sage >> --notebook=ipython so we have access to sage kernel. >> With the following link you sent to me it works. Apparently ssl is inside >> or at least it doesn't ask for ! >> I too installed all the libs you mentioned. But no way to get the deb >> working (pity but not dramatic), I have to install it by hand sudo mv sage >> /usr/share/sage and sudo ln -s /usr/share/sage/sage /usr/bin/sage (before >> delete sage in bin sudo rm /usr/bin/sage), but that's not ubuntu original >> installation : /usr/lib/sagemath (but it's helping me when something get >> wrong like at the moment !), so I have two sage installed in different >> location and when there is a problem I connect to the working version. >> Anticipating a little wily seems to have problems with dir path python >> but I might be working properly when ready. >> Anyway thanks for your great job. For me it's not too annoying and I >> don't want to give you more work than necessary, it's a only a whish that >> maybe others can have. I am not qualified enaugh to tell you what's the >> problem with ssl (In my opinion it's more a problem of right or directory >> than ssl as I have put all lib ?) >> Kind regards >> Henri >> >> >> >> Le 23/09/2015 11:42, Jan Groenewald a écrit : >> >> Hi >> >> On 23 September 2015 at 10:40, Henri Girard <henri.gir...@gmail.com> >> wrote: >> >>> I just test it, ssl is always lacking >>> But I am not sure this is the reason because libssl-dev is installed. >>> Why not put in deb the sage-6.8 LTS, I installed it and it works (that's >>> just a suggestion, but sorry if it's a bad idea ?) >>> Before I could compile sage but now I got errors that's why I like your >>> deb and it's automatically updated. >>> >> >> I think due to other problems on many platforms the ssl is disabled by >> default in the Sage binaries. Other sage developers are more qualified to >> discuss that and answer that. >> >> What is the "sage 6.8 LTS"? Do you mean include something other than >> http://sagemath.mirror.ac.za/linux/64bit/Ubuntu_14.04_LTS_sage-6.8-x86_64-Linux.tar.lrz >> in the PPA? Or do you mean depend on libssl-dev and include a rebuilt sage >> with pyopenssl in the deb? I coudl then be introducing errors/bugs to the >> downstream users if I include a rebuilt python with ssl. I want to confirm >> that it is possible though, with one or two lines, to add SSL capability. >> >> Our (AIMS) main use case, by the way, is standalone laptop installs, that >> can work offline, so we use a per-user installation, not a multi-user >> server, so the https is irrelevant for us. I'd like to stay close to the >> upstream with the PPA. We do however have students ssh from a laptop into >> their own account on a campus desktop to use a notebook on a more powerful >> machine or just to access their worksheets conveniently from their rooms. >> >> Right now we cannot on the -full package do either of >> >> sage -i pyopenssl >> or >> sage -pip install pyopenssl >> >> even though we did >> >> sudo apt-get install python-dev libffi-dev libssl-dev libxml2-dev >> libxslt1-dev >> >> Our >> >> sage -f python was succcesful though. >> >> What exactly are the commands and output of what you are trying to do? >> >> Regards, >> Jan >> >> >> -- >> .~. >> /V\ Jan Groenewald >> /( )\ www.aims.ac.za >> ^^-^^ >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "sage-release" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/sage-release/l-jhyDbkjNo/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> sage-release+unsubscr...@googlegroups.com. >> To post to this group, send email to sage-release@googlegroups.com. >> Visit this group at http://groups.google.com/group/sage-release. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sage-release" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to sage-release+unsubscr...@googlegroups.com. >> To post to this group, send email to sage-release@googlegroups.com. >> Visit this group at http://groups.google.com/group/sage-release. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > .~. > /V\ Jan Groenewald > /( )\ www.aims.ac.za > ^^-^^ > -- .~. /V\ Jan Groenewald /( )\ www.aims.ac.za ^^-^^ -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
