[Reportbug-maint] Bug#685824: reportbug: please add non-interactive mode

[Sandro Tosi]

On Sat, Aug 25, 2012 at 7:05 PM, Raphael Geissert <geissert at debian.org> wrote:
> On Saturday 25 August 2012 04:48:59 Sandro Tosi wrote:
>> On Fri, Aug 24, 2012 at 10:56 PM, Raphael Geissert <geissert at debian.org>
> wrote:
>> > It is currently impossible to use reportbug to non-interactively file
>> > bug reports. There are multiple issues for one of my use cases, but I
>> > will file them in other reports.
>>
>> can you be so kind to specify those usecases?
>
> Automatically filing bug reports when new issues are added to the security
> tracker.
> At the moment there's a script that generates a template but then it has to
> be manually edited and then piped to some MUA. I'd like to get rid of some
> of its parts and just hand the template over to reportbug (and in the
> specific case of auto-filing, avoiding all interactivity).

Ok, I meant: what is the exact (or the variation of it) command you're
running that doesn't give the non-interactive experience you're
describing? This way I'll have the precise use-case to verify if the
fix works or not.

>> > So, this one is a request to add an option that really makes reportbug
>> > non- interactive and files the bug report.
>>
>> mh, is this a meta-bug to fix all the other reports you filed?
>
> Not really, it was more a request to add an option (say --non-interactive),
> as --print and --template don't do quite what I'm requesting: being able to
> pass all the bug report information to reportbug so that it just puts it
> together and files it on the BTS.

Great, better then - I feared it was more "hey I have those other bugs
I'd like to have fixed so that this feature would work"

> The other bug reports are related. For instance, this bug could probably be
> fixed by adding another pseudo-ui that doesn't interact with the user and,
> instead, uses the default values for each prompt. If there's no default
> value, then it is an error and it aborts the whole thing.

I think much of the menus and questions can be skipped or answered on
the  cli, but I need the command causing problem to pin-points where
the problems are.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi