Re: Packaging the new upstream release of ipython (i.e. 1.1.0)
So there is a list of things that need doing for ipython. I'd built my own not-redistributable version of 1.1.0, (progress at https://github.com/detrout/debian-ipython) I'll see if I can help with some of the work listed below. Diane On Thursday, October 03, 2013 22:29:41 Jean-Christophe Jaskula wrote: > Hey, > > Thanks Thomas and Julian for your replies. Don't apologize for that, there > is no problem taking time to release something clean. BTW, I realize than I > was doing a package way simpler and dirtier than yours. > > I don't want to walk on anyone's toes or do unnecessary/redundant work. I'll > be happy to help and have a look at one of these libraries' license. I > can't promise to have a deep look quickly (i.e. next weekend) tho. > > Thanks, > JC > > Le 3 oct. 2013 à 13:24, Julian Taylor a écrit : > > Hi, > > sorry I am working very very slow in ipython, a reason is that there is > > no stable release on the horizon, so I have been slacking of a bit. > > Now that ubuntu 13.10 is almost out soon I have no excuse anymore :) > > > > The issue with ipython 1.1 is the large amount of third party javascript > > libraries it embeds. > > These are the libraries it needs (from bowser.json) and its status in > > > > debian: > >"bootstrap": "~2.3", > > > > in debian (libjs-twitter-bootstrap) but too old > > this is also hard to handle with packages so I currently plan to embed it. > > If you want to help out, please do a license/dfsg review of the embedded > > stuff and send me a debian/copyright file. > > > >"codemirror": "~3.15", > > > > in debian but far to old and in hardly usable state. > > ipython currently embeds so I am willing to continue with that. But also > > needs a new license review for 1.0. > > > >"font-awesome": "~3.1", > > > > debian package was not suitable, but was fixed recently, should be fine. > > Deian package needs adapting to use it. > > > >"jquery": "~2.0", > > > > 2.0 not in debian, hopefully will be soon. Maybe ipython also works with > > 1.7, didn't test that much yet. > > > >"jquery-ui": "~1.10", > > > > available in debian, packaging needs adapting to use it as 0.13.2 embeds > > a fork of it, fork not needed with 1.0 so far I know. > > > >"less.js": "~1.3", > > > > in debian, package needs adapting to use it (via fab) > > > >"marked": "~0.2.8", > > > > packaged for debian recently, ipython package needs adapting to use it. > > > >"requirejs": "~2.1" > > > > not in debian and looks like something that should be in debian (unlike > > bootstrap or codemirror it looks stable). > > Its not my area of expertise, help wanted. > > if none show up I'll probably go with embedding as I can't maintain a > > proper package of this. In this case needs a license review. > > > > On 03.10.2013 18:55, Jean-Christophe Jaskula wrote: > >> Hey, > >> > >> I haven't heard from any of you and I'm still a bit curious of the status > >> of the package. FYI, I continued patching and rearranging to fit with > >> the upstream sources. I got something which starts looking good to me. > >> > >> Hope to hear from you soon :-) > >> > >> Cheers, > >> JC > >> > >> Le 29 sept. 2013 à 16:31, Jean-Christophe Jaskula a écrit : > >>> Hi, > >>> > >>> The Ipython team has released a couple of major releases during the last > >>> months but I haven't seen any discussions about packaging them in > >>> debian. Just for curiosity, I decided to start trying to update the > >>> debian package (v0.13.2) to the latest release (v.1.1.0). When doing > >>> it, I realized there is a lot of changes to do and I do understand why > >>> it is not in sid yet (putting aside you might be also very busy with > >>> other things). > >>> > >>> I didn't plan to propose this work for a NMU but I'm wondering if > >>> someone was working on it. So far, my work is still in progress but I > >>> don't mind keeping working on it if it helps you or dropping it if a > >>> debian package is going to be uploaded soon. I have adapted most of the > >>> debian patches to the upstream release. I'm still working on the > >>> Mathjax patch to avoid ugly hack. I started from the source that one > >>> can get at: https://github.com/ipython/ipython/archive/rel-1.1.0.tar.gz > >>> . However, everything isn't shipped in this archive and I had to add > >>> "static components" that I took from: > >>> https://github.com/ipython/ipython/releases/download/rel-1.1.0/ipython-> > >>> >>> 1.1.0.tar.gz . I put these files altogether in the same .orig.tar.gz > >>> archive and started packaging from it. > >>> > >>> If you need help on this packaging, I'll be very happy to contribute. > >>> > >>> Cheers, > >>> JC > >>> > >>> PS: I'm attaching the debian folder for your information. > >>> > >>> -- > >>> Jean-Christophe Jaskula > > -- > Jean-Christophe Jaskula On Thursday, October 03, 2013 22:29:41 Jean-Christophe Jaskula wrote: > Hey, > > Thanks Thomas and Julian for your replies. Don't apologize for tha
Re: Packaging the new upstream release of ipython (i.e. 1.1.0)
Hey, Thanks Thomas and Julian for your replies. Don't apologize for that, there is no problem taking time to release something clean. BTW, I realize than I was doing a package way simpler and dirtier than yours. I don't want to walk on anyone's toes or do unnecessary/redundant work. I'll be happy to help and have a look at one of these libraries' license. I can't promise to have a deep look quickly (i.e. next weekend) tho. Thanks, JC Le 3 oct. 2013 à 13:24, Julian Taylor a écrit : > Hi, > sorry I am working very very slow in ipython, a reason is that there is > no stable release on the horizon, so I have been slacking of a bit. > Now that ubuntu 13.10 is almost out soon I have no excuse anymore :) > > The issue with ipython 1.1 is the large amount of third party javascript > libraries it embeds. > These are the libraries it needs (from bowser.json) and its status in > debian: > >"bootstrap": "~2.3", > in debian (libjs-twitter-bootstrap) but too old > this is also hard to handle with packages so I currently plan to embed it. > If you want to help out, please do a license/dfsg review of the embedded > stuff and send me a debian/copyright file. > >"codemirror": "~3.15", > in debian but far to old and in hardly usable state. > ipython currently embeds so I am willing to continue with that. But also > needs a new license review for 1.0. > >"font-awesome": "~3.1", > debian package was not suitable, but was fixed recently, should be fine. > Deian package needs adapting to use it. > >"jquery": "~2.0", > 2.0 not in debian, hopefully will be soon. Maybe ipython also works with > 1.7, didn't test that much yet. > >"jquery-ui": "~1.10", > available in debian, packaging needs adapting to use it as 0.13.2 embeds > a fork of it, fork not needed with 1.0 so far I know. > >"less.js": "~1.3", > in debian, package needs adapting to use it (via fab) > >"marked": "~0.2.8", > packaged for debian recently, ipython package needs adapting to use it. > >"requirejs": "~2.1" > not in debian and looks like something that should be in debian (unlike > bootstrap or codemirror it looks stable). > Its not my area of expertise, help wanted. > if none show up I'll probably go with embedding as I can't maintain a > proper package of this. In this case needs a license review. > > > > On 03.10.2013 18:55, Jean-Christophe Jaskula wrote: >> Hey, >> >> I haven't heard from any of you and I'm still a bit curious of the status of >> the package. FYI, I continued patching and rearranging to fit with the >> upstream sources. I got something which starts looking good to me. >> >> Hope to hear from you soon :-) >> >> Cheers, >> JC >> >> Le 29 sept. 2013 à 16:31, Jean-Christophe Jaskula a écrit : >> >>> Hi, >>> >>> The Ipython team has released a couple of major releases during the last >>> months but I haven't seen any discussions about packaging them in debian. >>> Just for curiosity, I decided to start trying to update the debian package >>> (v0.13.2) to the latest release (v.1.1.0). When doing it, I realized there >>> is a lot of changes to do and I do understand why it is not in sid yet >>> (putting aside you might be also very busy with other things). >>> >>> I didn't plan to propose this work for a NMU but I'm wondering if someone >>> was working on it. So far, my work is still in progress but I don't mind >>> keeping working on it if it helps you or dropping it if a debian package is >>> going to be uploaded soon. I have adapted most of the debian patches to the >>> upstream release. I'm still working on the Mathjax patch to avoid ugly >>> hack. I started from the source that one can get at: >>> https://github.com/ipython/ipython/archive/rel-1.1.0.tar.gz . However, >>> everything isn't shipped in this archive and I had to add "static >>> components" that I took from: >>> https://github.com/ipython/ipython/releases/download/rel-1.1.0/ipython-1.1.0.tar.gz >>> . I put these files altogether in the same .orig.tar.gz archive and >>> started packaging from it. >>> >>> If you need help on this packaging, I'll be very happy to contribute. >>> >>> Cheers, >>> JC >>> >>> PS: I'm attaching the debian folder for your information. >>> >>> -- >>> Jean-Christophe Jaskula >>> >>> >>> >>> >> >> -- Jean-Christophe Jaskula -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/0e44c86b-601a-4f58-9532-3e45f1f8d...@gmail.com
Re: Packaging the new upstream release of ipython (i.e. 1.1.0)
Hi, sorry I am working very very slow in ipython, a reason is that there is no stable release on the horizon, so I have been slacking of a bit. Now that ubuntu 13.10 is almost out soon I have no excuse anymore :) The issue with ipython 1.1 is the large amount of third party javascript libraries it embeds. These are the libraries it needs (from bowser.json) and its status in debian: "bootstrap": "~2.3", in debian (libjs-twitter-bootstrap) but too old this is also hard to handle with packages so I currently plan to embed it. If you want to help out, please do a license/dfsg review of the embedded stuff and send me a debian/copyright file. "codemirror": "~3.15", in debian but far to old and in hardly usable state. ipython currently embeds so I am willing to continue with that. But also needs a new license review for 1.0. "font-awesome": "~3.1", debian package was not suitable, but was fixed recently, should be fine. Deian package needs adapting to use it. "jquery": "~2.0", 2.0 not in debian, hopefully will be soon. Maybe ipython also works with 1.7, didn't test that much yet. "jquery-ui": "~1.10", available in debian, packaging needs adapting to use it as 0.13.2 embeds a fork of it, fork not needed with 1.0 so far I know. "less.js": "~1.3", in debian, package needs adapting to use it (via fab) "marked": "~0.2.8", packaged for debian recently, ipython package needs adapting to use it. "requirejs": "~2.1" not in debian and looks like something that should be in debian (unlike bootstrap or codemirror it looks stable). Its not my area of expertise, help wanted. if none show up I'll probably go with embedding as I can't maintain a proper package of this. In this case needs a license review. On 03.10.2013 18:55, Jean-Christophe Jaskula wrote: > Hey, > > I haven't heard from any of you and I'm still a bit curious of the status of > the package. FYI, I continued patching and rearranging to fit with the > upstream sources. I got something which starts looking good to me. > > Hope to hear from you soon :-) > > Cheers, > JC > > Le 29 sept. 2013 à 16:31, Jean-Christophe Jaskula a écrit : > >> Hi, >> >> The Ipython team has released a couple of major releases during the last >> months but I haven't seen any discussions about packaging them in debian. >> Just for curiosity, I decided to start trying to update the debian package >> (v0.13.2) to the latest release (v.1.1.0). When doing it, I realized there >> is a lot of changes to do and I do understand why it is not in sid yet >> (putting aside you might be also very busy with other things). >> >> I didn't plan to propose this work for a NMU but I'm wondering if someone >> was working on it. So far, my work is still in progress but I don't mind >> keeping working on it if it helps you or dropping it if a debian package is >> going to be uploaded soon. I have adapted most of the debian patches to the >> upstream release. I'm still working on the Mathjax patch to avoid ugly hack. >> I started from the source that one can get at: >> https://github.com/ipython/ipython/archive/rel-1.1.0.tar.gz . However, >> everything isn't shipped in this archive and I had to add "static >> components" that I took from: >> https://github.com/ipython/ipython/releases/download/rel-1.1.0/ipython-1.1.0.tar.gz >> . I put these files altogether in the same .orig.tar.gz archive and started >> packaging from it. >> >> If you need help on this packaging, I'll be very happy to contribute. >> >> Cheers, >> JC >> >> PS: I'm attaching the debian folder for your information. >> >> -- >> Jean-Christophe Jaskula >> >> >> >> > > -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/524da85d.4070...@googlemail.com
Re: Packaging the new upstream release of ipython (i.e. 1.1.0)
Hi Jean-Christophe, On 29 September 2013 13:31, Jean-Christophe Jaskula < jean.christophe.jask...@gmail.com> wrote: > The Ipython team has released a couple of major releases during the last > months but I haven't seen any discussions about packaging them in debian. > Just for curiosity, I decided to start trying to update the debian package > (v0.13.2) to the latest release (v.1.1.0). When doing it, I realized there > is a lot of changes to do and I do understand why it is not in sid yet > (putting aside you might be also very busy with other things). > > I didn't plan to propose this work for a NMU but I'm wondering if someone > was working on it. So far, my work is still in progress but I don't mind > keeping working on it if it helps you or dropping it if a debian package is > going to be uploaded soon. I have adapted most of the debian patches to the > upstream release. I'm still working on the Mathjax patch to avoid ugly > hack. I started from the source that one can get at: > https://github.com/ipython/ipython/archive/rel-1.1.0.tar.gz . However, > everything isn't shipped in this archive and I had to add "static > components" that I took from: > https://github.com/ipython/ipython/releases/download/rel-1.1.0/ipython-1.1.0.tar.gz. > I put these files altogether in the same .orig.tar.gz archive and started > packaging from it. > > If you need help on this packaging, I'll be very happy to contribute. > I asked Julian about this last month, and this is what he said: """ I'm not working very fast, due to lack of time and focus on other things :/ There are still a few things missing. highlightjs is done marked almost done still to do: fonts-awesome missing css files (#719360) requirejs bootstrap jquery 2.0 I don't know how to handle bootstrap as it has as version 3 out now ipython uses 2, debian has an even older 2. Probably embedding is best, like codemirror. If you want to help out you could have a look at packaging requirejs, it seems like a useful package as it has a small api (compared to bootstrap, jquery or codemirror). Also much appreciated is writing the debian/copyright for bootstrap if we go for the embed route. """ (I haven't got round to doing anything on this front yet) Thanks, Thomas
Re: Packaging the new upstream release of ipython (i.e. 1.1.0)
Hey, I haven't heard from any of you and I'm still a bit curious of the status of the package. FYI, I continued patching and rearranging to fit with the upstream sources. I got something which starts looking good to me. Hope to hear from you soon :-) Cheers, JC Le 29 sept. 2013 à 16:31, Jean-Christophe Jaskula a écrit : > Hi, > > The Ipython team has released a couple of major releases during the last > months but I haven't seen any discussions about packaging them in debian. > Just for curiosity, I decided to start trying to update the debian package > (v0.13.2) to the latest release (v.1.1.0). When doing it, I realized there is > a lot of changes to do and I do understand why it is not in sid yet (putting > aside you might be also very busy with other things). > > I didn't plan to propose this work for a NMU but I'm wondering if someone was > working on it. So far, my work is still in progress but I don't mind keeping > working on it if it helps you or dropping it if a debian package is going to > be uploaded soon. I have adapted most of the debian patches to the upstream > release. I'm still working on the Mathjax patch to avoid ugly hack. I started > from the source that one can get at: > https://github.com/ipython/ipython/archive/rel-1.1.0.tar.gz . However, > everything isn't shipped in this archive and I had to add "static components" > that I took from: > https://github.com/ipython/ipython/releases/download/rel-1.1.0/ipython-1.1.0.tar.gz > . I put these files altogether in the same .orig.tar.gz archive and started > packaging from it. > > If you need help on this packaging, I'll be very happy to contribute. > > Cheers, > JC > > PS: I'm attaching the debian folder for your information. > > -- > Jean-Christophe Jaskula > > > > -- Jean-Christophe Jaskula -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4955b122-9301-4337-ac9c-3a7071efc...@gmail.com
Packaging the new upstream release of ipython (i.e. 1.1.0)
Hi, The Ipython team has released a couple of major releases during the last months but I haven't seen any discussions about packaging them in debian. Just for curiosity, I decided to start trying to update the debian package (v0.13.2) to the latest release (v.1.1.0). When doing it, I realized there is a lot of changes to do and I do understand why it is not in sid yet (putting aside you might be also very busy with other things). I didn't plan to propose this work for a NMU but I'm wondering if someone was working on it. So far, my work is still in progress but I don't mind keeping working on it if it helps you or dropping it if a debian package is going to be uploaded soon. I have adapted most of the debian patches to the upstream release. I'm still working on the Mathjax patch to avoid ugly hack. I started from the source that one can get at: https://github.com/ipython/ipython/archive/rel-1.1.0.tar.gz . However, everything isn't shipped in this archive and I had to add "static components" that I took from: https://github.com/ipython/ipython/releases/download/rel-1.1.0/ipython-1.1.0.tar.gz . I put these files altogether in the same .orig.tar.gz archive and started packaging from it. If you need help on this packaging, I'll be very happy to contribute. Cheers, JC PS: I'm attaching the debian folder for your information. ipython_1.1.0-0+nmu1.debian.tar.gz Description: GNU Zip compressed data -- Jean-Christophe Jaskula