Re: nodoc solution HOWTO -- Avoid building Sphinx documentation on request (was: Bug#905750: RFS: elpy/1.23.0-1)

2018-09-05 Thread Nicholas D Steeves
Hi Niels, On Wed, Sep 05, 2018 at 05:45:00AM +, Niels Thykier wrote: [...] > Rather, I think there is a typo in changes. > > > --- > > debian/changelog | 6 ++ > > debian/control | 4 ++-- > > debian/rules | 8 +++- > > 3 files changed, 15 insertions(+), 3 deletions(-) > > >

Re: nodoc solution HOWTO -- Avoid building Sphinx documentation on request (was: Bug#905750: RFS: elpy/1.23.0-1)

2018-09-04 Thread Niels Thykier
Nicholas D Steeves: > Hi Ben and readers of debian-mentors, > > Solution at bottom. > > [...] > > "export DEB_BUILD_PROFILES=nodoc ; gbp buildpackage" does not work, > although I expect "DEB_BUILD_PROFILES=nodoc ; export > DEB_BUILD_PROFILES ; gbp buildpackage" should. > Rather, I think there

Re: nodoc solution HOWTO -- Avoid building Sphinx documentation on request (was: Bug#905750: RFS: elpy/1.23.0-1)

2018-09-04 Thread Nicholas D Steeves
Hi Ben and readers of debian-mentors, Solution at bottom. On Sat, Sep 01, 2018 at 08:26:07PM -0400, Nicholas D Steeves wrote: > On Fri, Aug 10, 2018 at 06:02:14AM +1000, Ben Finney wrote: > > Chris Lamb writes: > > > > > * You should probably avoid building the documentation too if the > > >

Re: Avoid building Sphinx documentation on request (was: Bug#905750: RFS: elpy/1.23.0-1)

2018-09-01 Thread Nicholas D Steeves
On Fri, Aug 10, 2018 at 06:02:14AM +1000, Ben Finney wrote: > Chris Lamb writes: > > > * You should probably avoid building the documentation too if the > >nodocs build profile is enabled. > > For packages from PyPI which have documentation detectable by > ‘dh_sphinxdoc’, does this (avoid

Bug#905750: RFS: elpy/1.23.0-1

2018-08-11 Thread Chris Lamb
[Not prematurely sending mail this time] Nicholas, Alas I wrote before, whilst I appreciate the sentiment, please spend any limited time you have for Debian work writing such things in suitable venue(s) and not in an adjunct sponsorship bug. Otherwise I fear the effort expended in such a

Bug#905750: RFS: elpy/1.23.0-1

2018-08-11 Thread Chris Lamb
Nicholas, > > For your wishlist/TODO: > > > > * Please fix "wrong-section-according-to-package-name" on your next > >upload (or otherwise fix Lintian). > > This is currently an Informational level message. When it was a > Warning I declared Section: lisp, even though I do not believe

Bug#905750: RFS: elpy/1.23.0-1

2018-08-10 Thread Nicholas D Steeves
Hi Chris, Thank you for sponsoring and reviewing! Reply follows inline. On Thu, Aug 09, 2018 at 08:06:43AM +0100, Chris Lamb wrote: > For your wishlist/TODO: > > * Please fix "wrong-section-according-to-package-name" on your next >upload (or otherwise fix Lintian). This is currently an

Avoid building Sphinx documentation on request (was: Bug#905750: RFS: elpy/1.23.0-1)

2018-08-09 Thread Ben Finney
Chris Lamb writes: > * You should probably avoid building the documentation too if the >nodocs build profile is enabled. For packages from PyPI which have documentation detectable by ‘dh_sphinxdoc’, does this (avoid building the documentation if the “nodocs” build profile is enabled) just

Bug#905750: RFS: elpy/1.23.0-1

2018-08-09 Thread Chris Lamb
tags 905750 + pending thanks Nicholas, > I am looking for a sponsor for my package "elpy" Uploaded elpy_1.23.0-1_amd64.changes. For your wishlist/TODO: * Please fix "wrong-section-according-to-package-name" on your next upload (or otherwise fix Lintian). * You should probably avoid

Bug#905750: RFS: elpy/1.23.0-1

2018-08-08 Thread Nicholas D Steeves
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "elpy" Hi Chris, I've CCed you because you've sponsored past releases. Package name: elpy Version : 1.23.0-1 Upstream Author : Jorgen Schaefer URL :