Bug#685824: reportbug: please add non-interactive mode
On Fri, Aug 24, 2012 at 4:56 PM, Raphael Geissert 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. the problem with --tag=security has been addressed in #685824, so if you just dont want output, I guess you can simply redirect to /dev/null, so I think that a cli like this: reportbug --subject "asdf" --severity normal --no-cc-menu --no-tags-menu -O --body='asdfsdf' --smtphost="" --tag=security --paranoid --no-security-team fulfill your request, correct? Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#685824: reportbug: please add non-interactive mode
On Saturday 25 August 2012 14:10:06 Sandro Tosi wrote: > 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. [...] > > 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. Just an example, working around the issue of --tag security, the version field part, and using --template: (some bits are probably redundant or innecessary, but this is what I came up with after checking all the options, one by one, on the man page) [.reportbugrc has mode, email address, and ui configured, the first to 'expert', the second to the one below, and the third to 'text'] $ env | grep ^DEB DEBEMAIL=geiss...@debian.org DEBFULLNAME=Raphael Geissert $ echo foo bar > /tmp/report.test $ reportbug --quiet --ui=text --mode=expert --no-verify --no-query-bts --no- check-available --no-debconf --no-check-installed --no-bug-script --no-tags- menu --no-cc-menu --src --package-version=' ' --severity=grave -- justification='security issue' -s 'vulnerability in foo' --body- file=/tmp/report.test --template asterisk ** (process:4250): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags' ** (process:4250): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags' ** (process:4250): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags' *** Welcome to reportbug. Use ? for help at prompts. *** Note: bug reports are publicly archived (including the email address of the submitter). Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'Raphael Geissert ' as your from address. Will send report to Debian (per lsb_release). Adding security tag to this report. Are you reporting an undisclosed vulnerability? If so, in order to responsibly disclose the issue, it should not be sent to the public BTS right now, but instead to the private Security Team mailing list. [y|N|q|?]? [I type y, then the email is displayed including the useless system information, and is followed by: ] If you want to provide additional information, please wait to receive the bug tracking number via email; you may then send any extra information to n...@bugs.debian.org (e.g. 999...@bugs.debian.org), where n is the bug number. Normally you will receive an acknowledgement via email including the bug report number within an hour; if you haven't received a confirmation, then the bug reporting process failed at some point (reportbug or MTA failure, BTS maintenance, etc.). In a non-interactive mode, I'd expect it to print nothing (I don't even know why there are those g-land warnings there) in case of success, and a warning to stderr and a non-zero status code in case of errors. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#685824: reportbug: please add non-interactive mode
On Sat, Aug 25, 2012 at 7:05 PM, Raphael Geissert wrote: > On Saturday 25 August 2012 04:48:59 Sandro Tosi wrote: >> On Fri, Aug 24, 2012 at 10:56 PM, Raphael Geissert > 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#685824: reportbug: please add non-interactive mode
On Saturday 25 August 2012 04:48:59 Sandro Tosi wrote: > On Fri, Aug 24, 2012 at 10:56 PM, Raphael Geissert 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). > > 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. 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. Just an idea. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#685824: reportbug: please add non-interactive mode
On Fri, Aug 24, 2012 at 10:56 PM, Raphael Geissert 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? > 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? Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#685824: reportbug: please add non-interactive mode
Package: reportbug Version: 5.0 Severity: wishlist Hi, 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. So, this one is a request to add an option that really makes reportbug non- interactive and files the bug report. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
