Re: Packaging pythonpy

2016-04-01 Thread Tiago Ilieve
Dmitry, On 31 March 2016 at 15:54, Dmitry Shachnev wrote: > Cool, one little change and it's much better! Actually this has one big implication: as it uses the same interpreter to evaluate its input, it becomes compatible with Python 3 expressions only. Noticed that after

Re: Packaging pythonpy

2016-03-31 Thread Florent Rougon
Hello, Dmitry Shachnev wrote: > Also, don't you think that /usr/bin/py is too generic? Maybe use > /usr/bin/pythonpy or something similar instead? (It's easy to change that, > as the linking is done by packaging rather than upstream buildsystem). Especially considering that

Re: Packaging pythonpy

2016-03-31 Thread Dmitry Shachnev
Hi Tiago, On Wed, Mar 30, 2016 at 09:03:07PM -0300, Tiago Ilieve wrote: >> Major nit about your package: did you read the Python policy, in particular >> the part that tells that all new packages should use Python 3 [3]? > > Actually I had consulted it, but not read it entirely. I don't know >

Re: Packaging pythonpy

2016-03-30 Thread Tiago Ilieve
Dmitry, On 30 March 2016 at 16:48, Dmitry Shachnev wrote: > Looks like I was a bit mistaken — dh_python2 will not replace shebangs for > files in /usr/share. But then you can do this manually using a sed call [1], > that is still easier than a patch. This is indeed way

Re: Packaging pythonpy

2016-03-30 Thread Dmitry Shachnev
Hi Tiago, On Wed, Mar 30, 2016 at 05:26:05AM -0300, Tiago Ilieve wrote: > On 29 March 2016 at 18:40, Dmitry Shachnev wrote: > > You do not need a patch for this kind of thing. Just pass > > --shebang=/usr/bin/whatever to dh_python2 call in your debian/rules. > > > > Also, for

Re: Packaging pythonpy

2016-03-30 Thread Tiago Ilieve
Hi Dmitry, On 29 March 2016 at 18:40, Dmitry Shachnev wrote: > You do not need a patch for this kind of thing. Just pass > --shebang=/usr/bin/whatever to dh_python2 call in your debian/rules. > > Also, for debian/packages, /usr/bin/pythonX is preferred over /usr/bin/env >

Re: Packaging pythonpy

2016-03-29 Thread Dmitry Shachnev
Hi, On Fri, Mar 25, 2016 at 09:00:46PM -0300, Tiago Ilieve wrote: > Tried one or two new approaches and it didn't worked. In the I've > created a patch[1] changing "#!/usr/bin/env python2" to > "#!/usr/bin/env python". You do not need a patch for this kind of thing. Just pass

Re: Packaging pythonpy

2016-03-25 Thread Tiago Ilieve
Gianfranco, On 25 March 2016 at 19:07, Gianfranco Costamagna wrote: > up to your sponsor :) Tried one or two new approaches and it didn't worked. In the I've created a patch[1] changing "#!/usr/bin/env python2" to "#!/usr/bin/env python". This should work as long

Re: Packaging pythonpy

2016-03-25 Thread Gianfranco Costamagna
Hi, >I really appreciate your effort in trying to package it yourself, but >you didn't solved the main problem, which is the >"python-script-but-no-python-dep". indeed, control file line two. it is an application, so choose some Section from there

Re: Packaging pythonpy

2016-03-25 Thread Tiago Ilieve
Hi Gianfranco, On 25 March 2016 at 16:21, Gianfranco Costamagna wrote: > http://debomatic-amd64.debian.net/distribution#unstable/pythonpy/0.4.4-1/lintian > please dget it from there and start again :) > > I fixed a lot of issues, and many more are there now! I

Re: Packaging pythonpy

2016-03-25 Thread Tiago Ilieve
Hi Gianfranco, On 25 March 2016 at 06:25, Gianfranco Costamagna wrote: > > adding python to the dependencies? > do you have python to build dependencies, dh-python and python:Depends on the > binary package? This is what is strange. I've made the following

Re: Packaging pythonpy

2016-03-25 Thread Gianfranco Costamagna
Hi Tiago, >* How to fix the "python-script-but-no-python-dep" lintian error? I've >tried with and without pybuild and the error still persists. adding python to the dependencies? do you have python to build dependencies, dh-python and python:Depends on the binary package? >* How to get

Re: Packaging pythonpy

2016-03-24 Thread Tiago Ilieve
Hi, Can someone please help me on this one? I'm pretty close to finish the initial packaging work. After fixing the following issues, it will be a matter of adding a manpage and filling a RFS. * How to fix the "python-script-but-no-python-dep" lintian error? I've tried with and without pybuild