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

[Raphael Geissert]

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

___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint

[Reportbug-maint] Bug#685825: reportbug: too noisy even when asking it to be --quiet

[Raphael Geissert]

Package: reportbug
Version: 5.0
Severity: minor

Hi,

In spite of passing --quiet I get the following, every single time, even when 
passing --ui=text:

8--8
** (process:8656): WARNING **: Trying to register gtype 'GMountMountFlags' as 
enum when in fact it is of type 'GFlags'

** (process:8656): WARNING **: Trying to register gtype 'GDriveStartFlags' as 
enum when in fact it is of type 'GFlags'

** (process:8656): 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 geiss...@debian.org' as your from address.
Will send report to Debian (per lsb_release).
8--8

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net

___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint

[Reportbug-maint] Bug#685826: reportbug: --tag=security can't be set even with --mode=expert

[Raphael Geissert]

Package: reportbug
Version: 5.0
Severity: normal

Hi,

Even if passing --mode=expert, --tag=security results in the following 
message:

 Ignored bogus setting for --tag: security

From a quick look at the code I see that there is a check for the mode 
before allowing the security tag to be set (blinndly?).

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net

___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint

[Reportbug-maint] Bug#685828: reportbug: package version can't be left blank

[Raphael Geissert]

Package: reportbug
Version: 5.0
Severity: minor

Hi,

There doesn't seem to be any way to omit the Version pseudo-header, which is 
valid when filing a bug against the BTS. If one passes --package-version=' ' 
it is accepted (and thus the version prompt avoided) but the header is still 
added:

 Version:  

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net

___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint

[Reportbug-maint] Bug#685827: reportbug: please add option to omit system information

[Raphael Geissert]

On Saturday 25 August 2012 04:47:29 Sandro Tosi wrote:
 Nope, sorry, I won't add an option to remove sysinfo (even in higher
 modes) because the risk to be abused is much higher than the
 (possible) benefits of not having them.

What kind of abuse do you have in mind?

Even for my personal use (and not that of other use cases I have in mind), 
it's one of the reasons why I rarely use reportbug: it unecessarily reveals 
certain system details.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net

___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint

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

[Raphael Geissert]

On Saturday 25 August 2012 04:48:59 Sandro Tosi wrote:
 On Fri, Aug 24, 2012 at 10:56 PM, Raphael Geissert geiss...@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).

  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

___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint

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

[Raphael Geissert]

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 geiss...@debian.org' 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

___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint

[Reportbug-maint] Bug#685828: reportbug: package version can't be left blank

[Raphael Geissert]

On Saturday 01 September 2012 16:40:02 Sandro Tosi wrote:
 Can you please specify what's the use case for not providing the
 version header? even the instruction on the BTS recommends to include
 it.

When the exact affected versions are not known (such as when a security issue 
is reported) it is best not to specify any version. That way it won't affect 
the package's testing migration or anything.

Once determined, the not/affected versions can be marked approprietly.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net

___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint

[Reportbug-maint] Bug#878088: reportbug: please inform security and lts teams about security update regressions

[Raphael Geissert]

Hi,

On 9 October 2017 at 19:47, Markus Koschany <a...@debian.org> wrote:
[...]
> If the bug is reported against a package with a version number that
> indicates a security update like +deb7u1 or ~deb8u3, both team mailing
> lists should be added to CC after the bug reporter confirms that this
> is a regression caused by a security update.

Perhaps reportbug could check the package's changelog to determine
whether the latest update was a security or LTS one. It could do so by
looking for the sec team's or LTS' snippet on the latest version.

Then and only then it could also ask for confirmation, as in: "is the
bug a recent regression?", and CC the corresponding team. For
instance, there's no need to CC the security team for regressions by
LTS updates.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net

___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint

[Reportbug-maint] Bug#878088: reportbug: please inform security and lts teams about security update regressions

[Raphael Geissert]

Hi,

On 6 Dec 2017 08:48, "Markus Koschany"  wrote:

I have updated the patch according to your suggestions. It's a bit
strange that we can't match release numbers and code name already. I
think it would be best to implement this feature somewhere else but for
the sake of moving forward the code will just fetch this json file now.


Isn't this provided already by the ftp-master API?
Other than that there's also the madison interface to UDD. There might even
be an API based on the new packages tracker, but I'm just guessing here.

Cheers,
___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint