Re: Packaging pythonpy
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 > pythonX. Thanks for the tip. I've tried to remove the referred patch and added "--shebang=/usr/bin/python" to the already existing "override_dh_python2". The problem is that with this modification the error "python-script-but-no-python-dep" comes up again. :-( Regards, Tiago. -- Tiago "Myhro" Ilieve Blog: https://blog.myhro.info/ GitHub: https://github.com/myhro LinkedIn: https://br.linkedin.com/in/myhro Montes Claros - MG, Brasil
Re: gphoto2 package name problem
On Mon, Feb 22, 2016 at 12:37 PM, Dmitry Shachnev wrote: > Hi Damon, > > On Sun, Feb 21, 2016 at 11:55:28PM +0500, Damon Lynch wrote: > > Good news: the developer of gphoto2-cffi has just confirmed that he is > happy > > for both the package name of his project to be renamed into > > "python-gphoto2cffi" in Debian, and for the currently unpackaged project > > "python-gphoto2" to be given the Debian package name his project > currently > > uses, "python-gphoto2". > > Great! > > Have you talked to the upstream developer or to the Debian maintainer? > I meant the latter in my previous message. > > As at the time of writing this email, the project "gphoto2-cffi" has not > > made a new release with the changed module name: > > https://github.com/jbaiter/gphoto2-cffi , although as I noted in my > previous > > email, it has made the necessary commit: > https://github.com/jbaiter/gphoto2-cffi/commit/6de87c88e56b59588fe1be48e9227dfa00382b91 > I'd like the help of a Debian packager / developer to rename a Debian package before Ubuntu 16.04 is released. Very likely also required is changing the name of the package's python module. The Debian package maintainer and upstream developer are in full agreement regarding the changes; all that is lacking is implementing it. Specifically, via email, I have confirmed that the Debian maintainer of the project "gphoto2-cffi"[1] agrees that its Debian package should be renamed to "python-gphoto2cffi" and that it's python module should be "gphoto2cffi". However the Debian maintainer says he/she been unable to make the changes himself because he/she is too busy. Meanwhile the next Ubuntu release is drawing ever closer. Thanks, Damon [1] https://github.com/jbaiter/gphoto2-cffi -- http://www.damonlynch.net
Re: Packaging pythonpy
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 debian/packages, /usr/bin/pythonX is preferred over /usr/bin/env > > pythonX. > > Thanks for the tip. I've tried to remove the referred patch and added > "--shebang=/usr/bin/python" to the already existing > "override_dh_python2". The problem is that with this modification the > error "python-script-but-no-python-dep" comes up again. :-( 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. Re Lintian error, this looks like a false positive. See [2]. Minor nit about your package: please build-depend on dh-python to get a modern version of dh_python2. 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]? [1] sed -i 's,^#!/usr/bin/.*,#!/usr/bin/python,' debian/pythonpy/usr/share/pythonpy/pythonpy/*.py [2] https://bugs.debian.org/743599 [3] https://www.debian.org/doc/packaging-manuals/python-policy/ch-python3.html -- Dmitry Shachnev signature.asc Description: PGP signature
Re: gphoto2 package name problem
Hi Damon,
On Wed, Mar 30, 2016 at 06:19:58PM +0500, Damon Lynch wrote:
> I'd like the help of a Debian packager / developer to rename a Debian
> package before Ubuntu 16.04 is released. Very likely also required is
> changing the name of the package's python module. The Debian package
> maintainer and upstream developer are in full agreement regarding the
> changes; all that is lacking is implementing it.
>
> Specifically, via email, I have confirmed that the Debian maintainer of the
> project "gphoto2-cffi"[1] agrees that its Debian package should be renamed
> to "python-gphoto2cffi" and that it's python module should be "gphoto2cffi".
> However the Debian maintainer says he/she been unable to make the changes
> himself because he/she is too busy. Meanwhile the next Ubuntu release is
> drawing ever closer.
This was not difficult — a debdiff is attached.
If you want this in Ubuntu 16.04, you need to file a feature freeze exception
request first (and preferably get the Debian maintainer to upload it first, so
that it can be synced).
--
Dmitry Shachnev
diff -ruN gphoto2-cffi-0.2/debian/changelog gphoto2-cffi-0.3a1/debian/changelog
--- gphoto2-cffi-0.2/debian/changelog 2015-10-25 08:11:12.0 +0100
+++ gphoto2-cffi-0.3a1/debian/changelog 2016-03-30 22:40:41.0 +0200
@@ -1,3 +1,13 @@
+gphoto2-cffi (0.3~a1~20160330-1) UNRELEASED; urgency=medium
+
+ * New upstream snapshot.
+ * Drop add-datafiles.diff, applied upstream.
+ * Binary packages renamed to python[3]-gphoto2cffi, following upstream.
+ * Do not attempt to run tests, as there are none.
+ * Remove unused code in debian/rules.
+
+ -- Dmitry Shachnev Wed, 30 Mar 2016 22:22:09 +0200
+
gphoto2-cffi (0.2-3) unstable; urgency=low
* Python 3.5 support (Closes: #793328)
diff -ruN gphoto2-cffi-0.2/debian/control gphoto2-cffi-0.3a1/debian/control
--- gphoto2-cffi-0.2/debian/control 2015-10-25 08:09:23.0 +0100
+++ gphoto2-cffi-0.3a1/debian/control 2016-03-30 22:37:55.0 +0200
@@ -5,18 +5,20 @@
Build-Depends: python-setuptools (>= 0.6b3), python3-setuptools, python-enum34, python-all (>= 2.6.6-3), python3-all, debhelper (>= 9), dh-python, python-cffi, python3-cffi, python-all-dev, python3-all-dev, libgphoto2-dev
Standards-Version: 3.9.6
-Package: python-gphoto2
+Package: python-gphoto2cffi
Architecture: any
Depends: ${misc:Depends}, ${python:Depends}, ${shlibs:Depends}
+Replaces: python-gphoto2
Description: GPhoto2 bindings with simpler API
Python bindings for libgphoto2 with an interface that strives to be idiomatic.
In contrast to other bindings for Python, gphoto2-cffi hides most of the
lower-level abstractions and reduces the API surface while still offering
access to most of the library's features.
-Package: python3-gphoto2
+Package: python3-gphoto2cffi
Architecture: any
Depends: ${misc:Depends}, ${python3:Depends}, ${shlibs:Depends}
+Replaces: python3-gphoto2
Description: GPhoto2 bindings with simpler API
Python bindings for libgphoto2 with an interface that strives to be idiomatic.
In contrast to other bindings for Python, gphoto2-cffi hides most of the
diff -ruN gphoto2-cffi-0.2/debian/patches/add-datafiles.diff gphoto2-cffi-0.3a1/debian/patches/add-datafiles.diff
--- gphoto2-cffi-0.2/debian/patches/add-datafiles.diff 2015-06-25 20:58:52.0 +0200
+++ gphoto2-cffi-0.3a1/debian/patches/add-datafiles.diff 1970-01-01 01:00:00.0 +0100
@@ -1,12 +0,0 @@
-Index: gphoto2-cffi-0.2/setup.py
-===
gphoto2-cffi-0.2.orig/setup.py
-+++ gphoto2-cffi-0.2/setup.py
-@@ -58,6 +58,7 @@ setup(
- license='LGPLv3',
- packages=['gphoto2'],
- include_package_data=True,
-+package_data={'':['gphoto2.cdef']},
- distclass=BinaryDistribution,
- setup_requires=['cffi'],
- install_requires=REQUIRES,
diff -ruN gphoto2-cffi-0.2/debian/patches/series gphoto2-cffi-0.3a1/debian/patches/series
--- gphoto2-cffi-0.2/debian/patches/series 2015-06-25 20:57:42.0 +0200
+++ gphoto2-cffi-0.3a1/debian/patches/series 1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-add-datafiles.diff
diff -ruN gphoto2-cffi-0.2/debian/rules gphoto2-cffi-0.3a1/debian/rules
--- gphoto2-cffi-0.2/debian/rules 2015-06-25 21:02:24.0 +0200
+++ gphoto2-cffi-0.3a1/debian/rules 2016-03-30 22:42:43.0 +0200
@@ -1,26 +1,6 @@
#!/usr/bin/make -f
-# This file was automatically generated by stdeb 0.8.2 at
-# Thu, 09 Oct 2014 22:55:33 +0300
-PYTHONS:=$(shell pyversions -vr)
-PYTHON3S:=$(shell py3versions -vr)
-export PYBUILD_NAME=gphoto2
+export PYBUILD_NAME=gphoto2cffi
+export PYBUILD_DISABLE=test
%:
dh $@ --with python2,python3 --buildsystem=pybuild
-
-override_dh_clean:
- dh_clean -O--buildsystem=pybuild
- rm -rf build
- rm -rf gphoto2/__pycache__
-
-override_dh_install:
- set -e ; for p
Re: Application to join Debian Python Modules Team
[Raoul Snyman, 2016-03-26] > My Alioth login is "superfly-guest" and I'm "superfly" in #debian-python > (I'm also part of the team arranging DebConf16). > > I have read https://python-modules.alioth.debian.org/policy.html and I > accept it. Welcome :) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 signature.asc Description: PGP signature
Re: Packaging pythonpy
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 clever than an entire patch to fix something so simple. :-) Done[1]. > Re Lintian error, this looks like a false positive. See [2]. You mean that maybe it's better if we add an override instead of a workaround? > Minor nit about your package: please build-depend on dh-python to get a modern > version of dh_python2. Done[2]. > 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 why but I thought that the Python 3 requirement was a *nice to have*, not a *should have*. Anyway, I've updated[3] the build system to use Python 3. I noticed that the test suite wasn't being properly executed and sent a patch to upstream[4]. As soon as a new release is made with this changed integrated, I'll be adding support for DEP-8 (as suggested by Barry Warsaw[5] in the last week), as they are functional tests that depends on the package being installed. I've uploaded the updated package to mentors.d.n[6], but I guess its better to wait for a new release integrating the test suite fixes. The upstream is pretty fast and responsive. Are you able to sponsor the upload when we finish taking care of those details? I've filled an RFS (#819289[7]), but forgot to add the "debian-python" mailing list in "X-Debbugs-CC". Regards, Tiago. [1]: https://github.com/myhro/deb-pythonpy/commit/f4ce711 [2]: https://github.com/myhro/deb-pythonpy/commit/868667b [3]: https://github.com/myhro/deb-pythonpy/commit/3c2f4bd [4]: https://github.com/Russell91/pythonpy/pull/79 [5]: https://lists.debian.org/debian-python/2016/03/msg00101.html [6]: http://mentors.debian.net/package/pythonpy [7]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819289 -- Tiago "Myhro" Ilieve Blog: https://blog.myhro.info/ GitHub: https://github.com/myhro LinkedIn: https://br.linkedin.com/in/myhro Montes Claros - MG, Brasil
