Bug#840249: want dput --no-lintian option
Ben Finney writes ("Re: Bug#840249: want dput --no-lintian option"):
> On Mon, 2016-10-10 01:26 +0100, Ian Jackson
> wrote:
> > tl/dr: Please provide
> > 1. Command line option --no-lintian to override run_lintian in config
> > 2. Convenient way to discover whether run_lintian is set in dput config
>
> Would an acceptable option:
>
> * Provide an alternate ‘dput’ configuration at run time
>
> satisfy? A tool that needs to use ‘dput’ non-interactively could
> specify the configuration to use, and thereby avoid whatever
> customisations the general configuration file has.
I did notice the --config option.
I don't think that's right for dgit. For example, I think if the user
has specified an alternative upload host, or even configured an
additional distro, dgit's dput ought to pick these things up.
Feel free to tell me you think I'm wrong about that...
Thanks,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#840249: want dput --no-lintian option
On Mon, 2016-10-10 01:26 +0100, Ian Jackson wrote: > tl/dr: Please provide > 1. Command line option --no-lintian to override run_lintian in config > 2. Convenient way to discover whether run_lintian is set in dput config Would an acceptable option: * Provide an alternate ‘dput’ configuration at run time satisfy? A tool that needs to use ‘dput’ non-interactively could specify the configuration to use, and thereby avoid whatever customisations the general configuration file has. -- \ `\ _o__) Ben Finney
Bug#840249: want dput --no-lintian option
Package: dput Version: 0.9.6.4 Control: block 827879 by -1 tl/dr: Please provide 1. Command line option --no-lintian to override run_lintian in config 2. Convenient way to discover whether run_lintian is set in dput config Explanation: dgit uses dput to do actual uploads. (This is useful because it means dgit does not need to replicate dput's configuration about upload queues, and also because it can sometimes mean that a partially-failed push/upload can be finished off.) dput can be configured to run lintian on every upload. lintian sometimes exits nonzero due to problems with the package. In the context of dgit this is not very helpful, because dput is run after the relevant git tags have been signed and pushed to the dgit git server. So the upload might fail halfway through: see #827879. dgit would like to disable this part of dput's functionality. However, dput does not honour a --no-lintian option to override the config file. Furthermore, if this option is specified, then I think it would be best if dgit actually honoured it, but at the right stage of the push. dgit could run dput --check-only, or could run lintian itself. But this should be done only if dput is configured with run_lintian, because the rest of dput's checks just duplicate things dgit does anyway. So dgit would like to know whether dput is configured to run lintian. Failing the above, how horrible would it be for dgit to put a stunt no-op lintian on PATH, when running dput ? Thanks, Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
