Bug#789712: RFS: pylint-celery/0.3-1 [ITP]
Hi Dmitry,
thanks for checking this over!
Yes, all right I've installed an override for dh_auto_test. However the test suite doesn't seem to be
complete and breaks on some missing things. I've contacted upstream if it's supposed to run somehow.
GPL short name changed.
I've wondered myself but I found that all Pylint (the main modules and the recently added
pylint-django and pylint-plugins-utils) happens with publically available libraries and therefore
I think is really expected being in /dist-packages/. There are things in the borderland of library
and app ... :-)
Daniel
On 24.06.2015 02:16, Dmitry Smirnov wrote:
> Hi Daniel,
>
> On Tue, 23 Jun 2015 20:20:34 Daniel Stender wrote:
>> I'm seeking for an uploader resp. sponsor of my package of pylint-celery
>
> I'm not sure if I'll be able to sponsor your package but I had a quick look
> and spotted a problem in packaging: it is incorrect to override
> DEB_BUILD_OPTIONS from "debian/rules". DEB_BUILD_OPTIONS should be available
> to whoever builds your package to override default behaviour (for example
> disable tests, etc.).
> Correct way to disable tests is by using "override_dh_auto_test" where
> you can invoke "-dh_auto_test" (that's right, with "minus" character) to run
> tests but continue on their failures. If some tests are meaningful it might be
> useful to run them in order to capture tests output in build logs.
>
> Also I believe the correct name of the license is "GPL-2" instead of
> "GPL-2.0".
>
> Finally I have some doubts whether this tiny plugin is worth exposing system-
> wide -- if it is only used by Pylint then perhaps it could be installed
> privately? Isn't that what Python team policy says?
>
--
http://qa.debian.org/developer.php?login=debian%40danielstender.com
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
Reply to: