[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1013254: reportbug: the --subject= CLI parameter ignored when -N is used



Package: reportbug
Version: 7.10.3
Severity: normal
X-Debbugs-Cc: debbug.reportbug@sideload.33mail.com

This command was run:

  $ reportbug -b --no-check-available -N 881955 --email="$email_address" --paranoid --draftpath="$my_draft_path" --subject='feedback' --no-cc

after having read this in the man page:

  -s SUBJECT, --subject=SUBJECT
     Set the subject of the bug report (i.e. a brief explanation of the
     problem, less than 60 characters).  If you do not specify this switch,
     you will be prompted for a subject.

The --subject parameter is ignored and reportbug prompts the user for a subject as follows:

  ===8<------------------------------
  …
  Looking up dependencies of reportbug...
  Getting status for related package python3-reportbug...
  Looking up 'depends' of related package python3-reportbug...
  Looking up 'suggests' of related package python3-reportbug...
  Getting changed configuration files...

  Please provide a subject for your response.
  [Re: reportbug: Subject header encoding not RFC2047-compliant (too long)]> 
  Does this bug still exist in version 7.10.3 of this package [y|N|q|?]? q
  …
  ===8<------------------------------

In this situation where a valid (<60 chars) subject is supplied, either:

  1. the supplied subject field should be used without prompting

  «OR»

  2. the prompt’s default should be the supplied subject with an option to override with the OP’s subject line.

In any case, it’s certainly wrong to ignore the --subject parameter
when a valid subject is supplied.

BTW, I was half-tempted to mark this as an accessibility issue because
someone who is handicapped might use the CLI options heavily to
mitigate the question/answer process. But I’m not sure if the impact
is significant.

-- Package-specific info:
** Environment settings:
EDITOR="emacs"
INTERFACE="text"

** /home/blee/.reportbugrc:
reportbug_version "7.10.3"
mode advanced
ui text
realname "anonymous coward"
no-cc
list-cc-me
smtphost reportbug.debian.org

-- System Information:
Debian Release: 11.0
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 'testing'), (990, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages reportbug depends on:
ii  apt                2.2.4
ii  python3            3.9.2-3
ii  python3-reportbug  7.10.3
ii  sensible-utils     0.0.14

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail                      <none>
pn  debconf-utils                   <none>
pn  debsums                         <none>
pn  dlocate                         <none>
ii  emacs-bin-common                1:27.1+1-3.1
ii  file                            1:5.39-3
ii  gnupg                           2.2.27-2
ii  postfix [mail-transport-agent]  3.5.6-1+b1
pn  python3-urwid                   <none>
pn  reportbug-gtk                   <none>
ii  xdg-utils                       1.1.3-4.1

Versions of packages python3-reportbug depends on:
ii  apt                2.2.4
ii  file               1:5.39-3
ii  python3            3.9.2-3
ii  python3-apt        2.2.1
ii  python3-debian     0.1.39
ii  python3-debianbts  3.1.0
ii  python3-requests   2.25.1+dfsg-2
ii  sensible-utils     0.0.14

python3-reportbug suggests no packages.

-- no debconf information

Reply to: