Re: Some thoughts about py{support,central} -> dh_python2 conversion
Hi all, On Tue, Nov 12, 2013 at 7:08 PM, Jakub Wilk wrote: >> sphinxcontrib: >> pymodules: [python-sphinxcontrib.issuetracker, >> python-sphinxcontrib.spelling] >> site-pkgs: [python-sphinxcontrib.actdiag, python-sphinxcontrib-pecanwsme, >> python-sphinxcontrib.seqdiag, python-sphinxcontrib-programoutput, >> python-sphinxcontrib.blockdiag, python-sphinxcontrib.nwdiag, >> python-sphinxcontrib-httpdomain, python-sphinxcontrib.phpdomain] > Work-around implemented in python-sphinx. I am currently experimenting¹ with porting sphinx to dh_python2. Do I get it correctly that the workaround should be kept so that dh_pysupport-using packages can integrate using dh_python2-based Sphinx? [¹]: http://packages.qa.debian.org/s/sphinx/news/20131006T183354Z.html -- Dmitry Shachnev -- 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/cakimphuyesmyougbaarkznl0y-hglyry4_e-4sx3pzh1re4...@mail.gmail.com
Re: CLI recommendations for version-specific /usr/bin scripts
Hi, On Mon, Nov 11, 2013 at 8:45 PM, Barry Warsaw wrote: > Am I missing anything? Can anybody improve on those rules above? Should we > just adopt them as our standard recommendation (not requirement)? I would also add this: * Do not use version-specific scripts unless there is real need for that. Nowadays when it's easy to get ‘python -m mymodule’ working, such scripts are provided mostly for compatibility purposes and create more problems than they solve. -- Dmitry Shachnev -- 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/cakimphx4hp-zi+ob7tyz2jvieo1dhraynkspjadc3nuxm0v...@mail.gmail.com
Re: problem with python-qt4 and python-qwt5-qt4
Hi, On Tue, Nov 12, 2013 at 9:55 PM, PICCA Frederic-Emmanuel wrote: > Hello, > > I am working on this bug [1] , after some investigration it seems that this > is a problem of incompatibility between > python-qwt5 and python-qt4. > > I do not know what is the best way to solve this issue. I have obtained a better stacktrace and sent it to upstream (pyqt) mailing list (as well as some debugging info), as it looks like a pyqt/sip problem to me. > rebuild python-qwt5-qt4 but python-qt4 should be fixed also to set the right > Breaks. The breaks are correct, you need to keep the binNMU version suffix when rebuilding. -- Dmitry Shachnev -- 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/CAKimPHW5Z0Y-P38eNdtJwr=zKCDMgc70=koqq6phbwgpvji...@mail.gmail.com
Re: debian/rules for packages using Cython
On 13 November 2013 19:42, Tim Michelsen wrote: >> Either don't use pybuild at clean stage with launchpad recipes, > How do I disable pybuild cleaning? > Please address your packaging questions to mailing list, either where this thread started. Or on debian mentors. If one is using dh(1), one should read how it works at dh(1) It accurately describes how that works, and how to override specific targets. pybuild, is simply implementation system for dh_auto_* based commands. How in general those work, see individual manpages for those, and debhelper(7) manpage for common build system options. Regards, Dmitrijs. -- 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/canbhluhnt0utcjil_h3qeuv5doj4w3lpl9j7wrmk7rw_ilw...@mail.gmail.com
Re: debian/rules for packages using Cython
> Please address your packaging questions to mailing list, either where > this thread started. > Or on debian mentors. Oops one wrong button. > If one is using dh(1), one should read how it works at dh(1) > It accurately describes how that works, and how to override specific targets. Thanks for no tips and no help. Yeah, RTFM is pretty cool. scattered & confusing documentation = no documentation. -- 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/l60oce$5rp$1...@ger.gmane.org
Re: Some thoughts about py{support,central} -> dh_python2 conversion
* Dmitry Shachnev , 2013-11-13, 23:15: sphinxcontrib: pymodules: [python-sphinxcontrib.issuetracker, python-sphinxcontrib.spelling] site-pkgs: [python-sphinxcontrib.actdiag, python-sphinxcontrib-pecanwsme, python-sphinxcontrib.seqdiag, python-sphinxcontrib-programoutput, python-sphinxcontrib.blockdiag, python-sphinxcontrib.nwdiag, python-sphinxcontrib-httpdomain, python-sphinxcontrib.phpdomain] Work-around implemented in python-sphinx. I am currently experimenting¹ with porting sphinx to dh_python2. Do I get it correctly that the workaround should be kept so that dh_pysupport-using packages can integrate using dh_python2-based Sphinx? That's right. -- 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/20131114070317.ga3...@jwilk.net
