Sponsorship ??

2012-11-07 Thread Joseph Mills
Hello there I am not sure that this is going to the correct team but here it goes. I found this upstream http://qt.gitorious.org/qt-labs/gimp-qmlexporter so I took it and packaged it. Now I want to get it into debian so that it will make its-way to Ubuntu. What the plugin does. It takes Gimp images

Re: Advise on packaging a new Python module

2012-11-07 Thread Simon McVittie
On 07/11/12 16:06, Tomás Di Domenico wrote: > On 07/11/12 16:43, Jakub Wilk wrote: >> * Tomás Di Domenico , 2012-11-07, 12:30: >>> About the different versions in the git repository and the upstream >>> package, that is actually my fault. I checked out the code from the >>> upstream Mercurial repos

Re: Advise on packaging a new Python module

2012-11-07 Thread Tomás Di Domenico
Right, that's what I meant. Poor wording on my side, sorry about that. Thanks! On 07/11/12 17:25, Dmitry Shachnev wrote: > On Wed, Nov 7, 2012 at 3:30 PM, Tomás Di Domenico wrote: >> Also, out of curiosity, is there ever the case where you will build a package >> against a particular build, with

Re: Advise on packaging a new Python module

2012-11-07 Thread Tomás Di Domenico
On 07/11/12 16:43, Jakub Wilk wrote: > * Tomás Di Domenico , 2012-11-07, 12:30: >> About the different versions in the git repository and the upstream >> package, that is actually my fault. I checked out the code from the >> upstream Mercurial repository and built the tarball myself, hence >> using

Re: Advise on packaging a new Python module

2012-11-07 Thread Dmitry Shachnev
On Wed, Nov 7, 2012 at 3:30 PM, Tomás Di Domenico wrote: > Also, out of curiosity, is there ever the case where you will build a package > against a particular build, without it being officially released by upstream? You mean packaging snapshots from upstream VCS, right? That is possible, but I w

Re: Advise on packaging a new Python module

2012-11-07 Thread Jakub Wilk
* Tomás Di Domenico , 2012-11-07, 12:30: About the different versions in the git repository and the upstream package, that is actually my fault. I checked out the code from the upstream Mercurial repository and built the tarball myself, hence using a more recent version than the one in the tarb

Re: Advise on packaging a new Python module

2012-11-07 Thread Tomás Di Domenico
Thank you very much for your input, Jakub and Dmitry. I'll start working on those changes right away. And yes, it would be very nice to try and get a Python3 version up. In fact, I'm quite interested in learning how to manually write the code, without dh (though I foresee it will take me some time

Re: Advise on packaging a new Python module

2012-11-07 Thread Jakub Wilk
* Dmitry Shachnev , 2012-11-07, 13:35: Maybe it's too pedantic, but here is what I can add to Jakub's comments: - no dependency on ${python:Depends}, please add it; This is one is certainly not too pendantic; it's a serious problem. Thanks for spotting it. - debian/docs is empty, please e

Re: Advise on packaging a new Python module

2012-11-07 Thread Dmitry Shachnev
Hi Tomás, Maybe it's too pedantic, but here is what I can add to Jakub's comments: - no dependency on ${python:Depends}, please add it; - debian/docs is empty, please either fill it or delete the file. On Sun, Nov 4, 2012 at 6:43 PM, Tomás Di Domenico wrote: > Greetings. > > I've recently joine