Re: Packaging pythonpy
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!
cheers,
G.
Il Venerdì 25 Marzo 2016 18:48, Tiago Ilieve <tiago.myhro@gmail.com> ha scritto:
Hi Gianfranco,
On 25 March 2016 at 06:25, Gianfranco Costamagna
<costamagnagianfranco@yahoo.it> 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 changes:
-
diff --git a/debian/control b/debian/control
index f0c1b3f..5205298 100644
--- a/debian/control
+++ b/debian/control
@@ -3,6 +3,7 @@ Section: python
Priority: optional
Maintainer: Tiago Ilieve <tiago.myhro@gmail.com>
Build-Depends: debhelper (>= 9),
+ dh-python,
python (>= 2.7.3),
python-setuptools (>= 0.6.24)
Standards-Version: 3.9.7
@@ -13,7 +14,9 @@ Vcs-Browser: https://github.com/myhro/deb-pythonpy
Package: pythonpy
Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: python (>= 2.7.3),
+ ${misc:Depends},
+ ${python:Depends}
Description: 'python -c', with tab completion and shorthand
pythonpy is an utility that facilitates the usage of Python one-liners. The
command 'py' evaluates a string consisting of any Python expression. It can do
-
But this didn't helped at all. The lintian.d.o page for
"python-script-but-no-python-dep"[1] says:
"Packages with Python scripts should depend on the package python.
Those with scripts that specify a specific version of Python must
depend on that version of Python (exactly).
For example, if a script in the package uses #!/usr/bin/python, the
package needs a dependency on python. If a script uses
#!/usr/bin/python2.6, the package needs a dependency on python2.6. A
dependency on python (>= 2.6) is not correct, since later versions of
Python may not provide the /usr/bin/python2.6 binary."
What is the "exactly" version of Python for a script which has
"#!/usr/bin/env python2" as its shebang?
> it is generated *during/after* the build, so the clean target won't work.
>
> a "package.pyremove" file might help, not sure
>
> codesearch.debian.net might help
> egg path:pyremove$
>
> https://codesearch.debian.net/results/egg%20path%3Apyremove%24/page_0
"pyremove" didn't worked, but in the same page that I found references
to it[2], there's a suggestion to override "dh_python", which is what
I did[3]. Thanks for the suggestion. :-)
Regards,
Tiago.
[1]: https://lintian.debian.org/tags/python-script-but-no-python-dep.html
[2]: https://wiki.debian.org/Python/LibraryStyleGuide#Python_3.3.2F3.4_unittest_fixers_for_2to3
[3]: https://github.com/myhro/deb-pythonpy/commit/68db18e
--
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
LinkedIn: https://br.linkedin.com/in/myhro
Montes Claros - MG, Brasil
Reply to: