Re: Build separate binary packages from single source
[Ben Finney, 2015-02-25] * name your tarballs like this (dpkg-source will unpack them to the right dir later) devpi_2.1.0.orig.tar.gz devpi_2.1.0.orig-client.tar.gz devpi_2.1.0.orig-server.tar.gz devpi_2.1.0.orig-web.tar.gz What tarballs? The source is distributed by upstream as a single sdist tarball. PyPI link you mentioned points to these: https://pypi.python.org/packages/source/d/devpi-server/devpi-server-2.1.4.tar.gz#md5=c92749708b957922f30bc7af0fb8a7b0 https://pypi.python.org/packages/source/d/devpi-web/devpi-web-2.2.3.tar.gz#md5=323fed68d7d1cef1f78c774d1d59e45f https://pypi.python.org/packages/source/d/devpi-client/devpi-client-2.0.5.tar.gz#md5=7075078c7b23f343adecd70e93885118 Are you implying I should manually split the sdist in a repack step? no, I suggest to create Debian source package out of original upstream tarballs -- 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: Digital signature
Re: Two more Python libraries
Hi,
[Tomasz Buchert, 2015-02-22]
I've packaged two Python modules:
* http://anonscm.debian.org/cgit/collab-maint/python-pyelftools.git/
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778933
* binary package names should be python-elftools and python3-elftools as
module name is elftools (and not pyelftools)
* why Priority: extra? I'd use optional (i.e. the default one, see docs¹)
* python-pyelftools is arch: any yet the description starts with
pure-python2 - shoudln't it be arch:all?
* same for python3-pyelftools
* if you add python{,3}-all-dev instead of python{,3}-dev to
* Build-Depends, pybuild will try to build/test this package for all
supported (c)Python interpreter versions
* python3-setuptools is missing in Build-Depends, please test your
package in sbuild (or similar tool)
[1]
https://www.debian.org/doc/manuals/debian-faq/ch-pkg_basics.en.html#s-priority
* http://anonscm.debian.org/cgit/collab-maint/python-guess-language.git
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778992
(at the moment of writing this, the second repository has not been yet
picked by cgit)
I guess I should join the Python Modules Team, right? What should I do?
https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin
please note that git is not allowed (yet, soon to be changed)
--
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: Digital signature
Re: Build separate binary packages from single source
On 25 February 2015 at 10:14, Piotr Ożarowski pi...@debian.org wrote: PyPI link you mentioned points to these: https://pypi.python.org/packages/source/d/devpi-server/devpi-server-2.1.4.tar.gz#md5=c92749708b957922f30bc7af0fb8a7b0 https://pypi.python.org/packages/source/d/devpi-web/devpi-web-2.2.3.tar.gz#md5=323fed68d7d1cef1f78c774d1d59e45f https://pypi.python.org/packages/source/d/devpi-client/devpi-client-2.0.5.tar.gz#md5=7075078c7b23f343adecd70e93885118 I just noticed https://pypi.python.org/pypi/devpi/ is just an empty shell and useless by itself. drwxrwxr-x hpk/hpk 0 2014-09-22 20:46 devpi-2.1.0/ drwxrwxr-x hpk/hpk 0 2014-09-22 20:46 devpi-2.1.0/devpi.egg-info/ -rw-rw-r-- hpk/hpk 1 2014-09-22 20:46 devpi-2.1.0/devpi.egg-info/not-zip-safe -rw-rw-r-- hpk/hpk 1 2014-09-22 20:46 devpi-2.1.0/devpi.egg-info/top_level.txt -rw-rw-r-- hpk/hpk 81 2014-09-22 20:46 devpi-2.1.0/devpi.egg-info/requires.txt -rw-rw-r-- hpk/hpk1635 2014-09-22 20:46 devpi-2.1.0/devpi.egg-info/PKG-INFO -rw-rw-r-- hpk/hpk 221 2014-09-22 20:46 devpi-2.1.0/devpi.egg-info/SOURCES.txt -rw-rw-r-- hpk/hpk 1 2014-09-22 20:46 devpi-2.1.0/devpi.egg-info/dependency_links.txt -rw-rw-r-- hpk/hpk 59 2014-09-22 20:46 devpi-2.1.0/setup.cfg -rw-rw-r-- hpk/hpk 46 2014-09-22 20:46 devpi-2.1.0/MANIFEST.in -rw-rw-r-- hpk/hpk1635 2014-09-22 20:46 devpi-2.1.0/PKG-INFO -rw-rw-r-- hpk/hpk 174 2014-09-22 20:46 devpi-2.1.0/tox.ini -rw-rw-r-- hpk/hpk 785 2014-09-22 20:46 devpi-2.1.0/README.rst -rw-rw-r-- hpk/hpk 28599 2014-09-22 20:46 devpi-2.1.0/CHANGELOG -rw-rw-r-- hpk/hpk1153 2014-09-22 20:46 devpi-2.1.0/setup.py I suspect you need these instead. http://pypi.python.org/pypi/devpi-server http://pypi.python.org/pypi/devpi-web http://pypi.python.org/pypi/devpi-client As each one has its own version number, and presumably its own release cycle, presumably you should be packaging them as separate Debian source packages. -- Brian May br...@microcomaustralia.com.au
Re: dh_python2 extension rename breaking module loading
[Matthias Klose, 2015-02-12] The interpreter doesn't look up the old module name with the multiarch suffix. Best thing would be to rename it manually (removing the module substring. Of course dh_python2 could do that as well. dh_python3 already does that for Python = 3.2. Last time I checked it wasn't needed for Python 2.X. I'll test it later and enable it in dh_python2 as well if it's really needed -- 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: Digital signature
Re: Request to join Python Modules Packaging Team
[Riley Baird, 2015-02-20] I would like to adopt the slides package as part of the Python Modules Packaging Team. Much of the work has already been done, and great! welcome :) the only things left would be to change the maintainer fields and move the repository over to Alioth. You can see the work I've already done please note that we're still using SVN (that will change, but if you want to use git now, please don't add such package to DPMT) here: https://mentors.debian.net/package/slides * why Priority: extra? shouldn't it be optional? (maybe except -doc package) * just a hint: you can use debian/slides-doc.examples to make debian/rules even simpler -- 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: Digital signature
Re: Build separate binary packages from single source
[Ben Finney, 2015-02-23]
I am working to package a collection of related Python distributions,
that are all distributed as a single source distribution
URL:https://pypi.python.org/pypi/devpi/.
The source distribution contains a collection of sub-distributions that
also get uploaded to PyPI. Each one has its own ‘setup.py’ in a
sub-directory.
That differs from the default expectations of Debhelper and Pybuild (it
does not build a single binary distribution from a single top-level
‘setup.py’).
What is the correct way to convince Debhelper, Pybuild, dh_python{2,3},
etc. to work with this source package and build the right binary
packages?
hints: (I didn't test it)
* name your tarballs like this (dpkg-source will unpack them to the
right dir later)
devpi_2.1.0.orig.tar.gz
devpi_2.1.0.orig-client.tar.gz
devpi_2.1.0.orig-server.tar.gz
devpi_2.1.0.orig-web.tar.gz
* in debian/rules use:
export PYBUILD_NAME=devpi
%:
dh $@ --with python2,python3 --buildsystem=pybuild
--sourcedirectory=server
dh $@ --with python2,python3 --buildsystem=pybuild
--sourcedirectory=client
dh $@ --with python2,python3 --buildsystem=pybuild --sourcedirectory=web
--
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: Digital signature
Re: Build separate binary packages from single source
Piotr Ożarowski pi...@debian.org writes: hints: (I didn't test it) Thanks for the suggestions. * name your tarballs like this (dpkg-source will unpack them to the right dir later) devpi_2.1.0.orig.tar.gz devpi_2.1.0.orig-client.tar.gz devpi_2.1.0.orig-server.tar.gz devpi_2.1.0.orig-web.tar.gz What tarballs? The source is distributed by upstream as a single sdist tarball. Are you implying I should manually split the sdist in a repack step? -- \ “All my life I've had one dream: to achieve my many goals.” | `\—Homer, _The Simpsons_ | _o__) | Ben Finney -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/85egpe7vrm@benfinney.id.au
Re: Build separate binary packages from single source
Brian May br...@microcomaustralia.com.au writes: I just noticed https://pypi.python.org/pypi/devpi/ is just an empty shell and useless by itself. The source VCS for ‘devpi’ contains the code base for all the others, which is why I hoped to use it. I'd still like to know how that should be done: package multiple Python distributions from a single upstream tarball. -- \ “Hey Homer! You're late for English!” “Pff! English, who needs | `\ that? I'm never going to England!” —Barney Homer, _The | _o__)Simpsons_ | Ben Finney -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/85a9027t0n@benfinney.id.au
