RE : Bits from the Sphinx maintainer
> In python-sphinx 1.0.7+dfsg-1 I made a few important changes:
> 3) There is a new helper tool, dh_sphinxdoc, which helps with packaging
> Sphinx-generated documentation. More specifically:
> - it does a few sanity checks (e.g. for missing files that are
> needed for the JavaScript to work);
> - it replaces known *.js files with symlinks to files to
> /usr/share/javascript/sphinxdoc/ and generates ${sphinxdoc:Depends}
> substitution variable;
> - removes some cruft (.doctree/, .buildinfo).
Thanks for this it will ease at least my life a lot.
could you add in the man page the thinks to do to migrate a package to use this
helper, the same way it was done for dh_python2.
> If your package builds documentation using Sphinx, I highly recommend
> you to stop creating jquery.js symlink with dh_link (or such) and use
> dh_sphinxdoc instead. This is the only future-proof way to have
> fully-functional, policy compliant package with Sphinx-built
> documentation.
I tryed it for one of my package.
I faced this "issue".
the setup.py file of the upstream was generating the doc during the build
process and install
it under the build/lib.xxx
so at the end all the documentation was under
/usr/share/pyshare//doc/...
As dh_sphinxdoc is called before dh_python2, It could not find the
documentation in the package.
so my question is
what is the right way to integrate sphinx generation doc in the build process
using setup.py
that way I should propose this to the upstream and keep my dh script as simple
as possible.
dh $@ --with python2 --with sphinxdoc
thanks
Frederic
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/a2a20ec3b8560d408356cac2fc148e5320a67...@sun-dag1.synchrotron-soleil.fr
Re: RE : Bits from the Sphinx maintainer
* PICCA Frédéric-Emmanuel , 2011-08-08, 07:45: If your package builds documentation using Sphinx, I highly recommend you to stop creating jquery.js symlink with dh_link (or such) and use dh_sphinxdoc instead. This is the only future-proof way to have fully-functional, policy compliant package with Sphinx-built documentation. I tryed it for one of my package. I faced this "issue". the setup.py file of the upstream was generating the doc during the build process and install it under the build/lib.xxx so at the end all the documentation was under /usr/share/pyshare//doc/... This is pretty weird place for documentation. dh_sphinxdoc by default looks only into subdirectories of /usr/share/doc/, but you can tell it to look somewhere else. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110808085053.gb4...@jwilk.net
RE : RE : Bits from the Sphinx maintainer
> This is pretty weird place for documentation. dh_sphinxdoc by default > looks only into subdirectories of /usr/share/doc/, but you can tell it > to look somewhere else. I tryed but then comes the problem presented in the previous mail dh_sphinxdoc is executed before dh_python2. Maybe we should also propose a policy for the sphinx documentation : put it in a standardize location /usr/share/doc//html ? /usr/share/doc//html ? /usr/share/sphynx/docs/ ? that way it should be possible to use sphinx-interlink between package. If I remember correctly the debian policy do not allow to rely on presence of files under /usr/share/doc, so where should we put the python documentation. I also know non-python package that are using sphinx for there own documentation. It should be possible also to use dh_sphinxdoc for them. Is it ? Frederic -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/a2a20ec3b8560d408356cac2fc148e5320a71...@sun-dag1.synchrotron-soleil.fr
Re: Some thoughts about py{support,central} -> dh_python2 conversion
I'm just getting back from vacation, so I'm playing catch-up right now. Thanks for sending this email. On Aug 07, 2011, at 10:29 PM, Jakub Wilk wrote: >1) Test your packages. Don't assume that the helper you use does the right >thing. Sometimes it does, sometimes it doesn't. One thing I've found very helpful is to build the package both before and after your conversion, then diff the package contents using debdiff. Once you get the hang of the expected differences, such as symlinks that will appear in only the post-conversion package, you can pretty quickly identify major problems in your conversion. Once this looks pretty good, installing the package and doing other tests as Jakub suggests will find any additional problem. >2) Do not skip the "Before you begin"[0] step. This is very important: if two >packages share a namespace, either both or none of them must use >python-support. Also, it's not enough just to convert them all to dh_python2: >you must make sure (using Breaks or Depends relationships) that you cannot >co-install an older python-support-based versions together with >dh_python2-based ones. I've added a note about Breaks/Depends to the wiki page. -Barry signature.asc Description: PGP signature
Re: reportbug says "python is a dependency package"
On Aug 07, 2011, at 10:28 AM, Jakub Wilk wrote: >* Piotr Ożarowski , 2011-08-07, 10:07: >>>"reportbug python" reports that "python is a dependency package". >>I >>>don't know what a dependency package is but "python" seems a >>classic >>>binary package to me. Where should this bug reported? > >I believe it's a feature, not a bug. This is to prevent people from reporting >bugs in the Python interpreter against the python package. Wow, that's really useful information to convey, but I'm not sure the warning actually does that very well. I guess fixing that should start with a bug report on reportbug. ;) -Barry signature.asc Description: PGP signature
please join me to the team
Hi, could you add me to alioth (osallou-guest) so that I add a new package (this is a dependency for an other package to come). I filled an ITP for this module: Bug#637109: Acknowledgement (ITP: pycaptcha -- collection of Python modules implementing CAPTCHAs) I already maintain other packages in other teams (debian-med mainly). Thanks Olviier
Re: reportbug says "python is a dependency package"
OoO Vers la fin de l'après-midi du lundi 08 août 2011, vers 16:22, Barry Warsaw disait : "reportbug python" reports that "python is a dependency package". I don't know what a dependency package is but "python" seems a classic binary package to me. Where should this bug reported? >> >> I believe it's a feature, not a bug. This is to prevent people from reporting >> bugs in the Python interpreter against the python package. > Wow, that's really useful information to convey, but I'm not sure the warning > actually does that very well. > I guess fixing that should start with a bug report on reportbug. ;) It seems that it is the BTS which declares python as a "dependency package". Maybe this makes more sense for other packages. I still need to find the list of "deppkgs" to check what kind of packages is here. -- Vincent Bernat ☯ http://vincent.bernat.im Write clearly - don't sacrifice clarity for "efficiency". - The Elements of Programming Style (Kernighan & Plauger) pgpyRoBKTfAYe.pgp Description: PGP signature
Python 3 BoF at DebConf11
At DebConf11 in Banja Luka, we had a short discussion¹ about Python 3 support in Debian. Apparently everything is very good, nobody complained², no feature request for dh_python3... so I talked a little bit about PEP 3147, PEP 3149, new and shiny PEP 402 and about status of py3multibuild GSoC project (which already supports more build systems than dh/cdbs, Mesutcan is working on integrating it with CDBS/dh sequencer now). We discussed /usr/bin/python2 symlink issue shortly and we all agreed that we don't want Debian to use it (should helpers change shebangs back to /usr/bin/python? Should lintian warn about it?) although we might want to ship it with Wheezy to follow other distributions³. /usr/bin/python will point to Python 2 in Debian for a while (Wheezy and Wheezy+1 for sure). /usr/bin/python3 might point to python3.3 instead of 3.2, though. Python 3.3 should be released short after Wheezy freeze, but we'll have RC releases in unstable before the freeze and it could be possible to replace 3.2 with 3.3 in supported Python 3 versions (but that's something we'll consider later, after checking how much work is needed for the transition). The good news is that Andreas will port britney⁴ to Python 3 really soon now (but I might misunderstood something, as usual ;-) Anyway, it should be a lot easier to add python3-* packages in 1-2 months (py3build will be integrated in python3-defaults package and dh_python3 will get some improvements). [¹] unfortunately gobby.debian.net was shutdown after DebConf, anyone has a copy of dc11-python3-bof and a list of participants? [²] last minute meetings FTW! ;-) [³] /me will still try to convince others to NOT do that, unless we will actually switch ALL scripts to python2 (so that users who will be tempted to change /usr/bin/python symlink, will not break their systems) [⁴] git://anonscm.debian.org/tools-release/britney2.git -- 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: Python 3 BoF at DebConf11
* Piotr Ożarowski , 2011-08-08, 23:50: We discussed /usr/bin/python2 symlink issue shortly and we all agreed that we don't want Debian to use it (should helpers change shebangs back to /usr/bin/python? Should lintian warn about it?) I'm surprised to see that lintian doesn't already emit unusual-interpreter. I believe it should. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110808230826.ga5...@jwilk.net
Re: Python 3 BoF at DebConf11
* Jakub Wilk , 2011-08-09, 01:08: We discussed /usr/bin/python2 symlink issue shortly and we all agreed that we don't want Debian to use it (should helpers change shebangs back to /usr/bin/python? Should lintian warn about it?) I'm surprised to see that lintian doesn't already emit unusual-interpreter. I believe it should. ...it does emit python-script-but-no-python-dep, though. (This code is pretty weird. :/) -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110809001222.ga8...@jwilk.net
-dbg packages
Hi! Is this page up-to-date? http://wiki.debian.org/Python/DbgBuilds Does dh_python2 handle this part itself now? -- Vincent Bernat ☯ http://vincent.bernat.im Make input easy to proofread. - The Elements of Programming Style (Kernighan & Plauger) pgpB8brVrfl7W.pgp Description: PGP signature
