Package: reportbug Version: 7.10.3+deb11u1 Followup-For: Bug #1014871 X-Debbugs-Cc: [email protected]
Indeed I concur. If this bug report were on Launchpad I would be upvoting it (which I think is not possible in debian bug reports). Calling reportbug -r “confusing” is putting it overly lightly. The -r option is actually completely broken & useless. There are several bugs which should probably be reported separately. This is what my session looked like: ===8<------------------------------ $ torsocks reportbug -r "$saved_report" 1658731266 WARNING torsocks[21461]: [syscall] Unsupported syscall number 315. Denying the call (in tsocks_syscall() at syscall.c:604) *** 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 'anonymous coward <foo@a5dbkgvakon2lxamlueiizkv6i3s36wpw3i32a63bu4xmtcnbdttmryd.onion>' as your from address. Will send report to Debian (per lsb_release). Spawning emacs... 1658731267 WARNING torsocks[21486]: [syscall] Unsupported syscall number 315. Denying the call (in tsocks_syscall() at syscall.c:604) No changes were made in the editor. Report will be sent to Debian Bug Tracking System <[email protected]> Submit this report on reportbug (e to edit) [y|n|a|c|E|i|l|m|p|q|d|tSubmit this report on reportbug (e to edit) [y|n|a|c|E|i|l|m|p|q|d|t|?]?Submit this report on reportbug (e to edit) [y|n|a|c|E|i|l|m|p|q|d|t|?]? y Report is unchanged. Edit this report or quit [E|q|s|?]? s Sending empty report anyway... 1658731287 ERROR torsocks[21461]: Unable to resolve. Status reply: 4 (in socks5_recv_resolve_reply() at socks5.c:677) Saving a backup of the report at /tmp/reportbug-reportbug-backup-20220725084127-j_q_q9m2 Connecting to reportbug.debian.org via SMTP... 1658731289 ERROR torsocks[21461]: Unable to resolve. Status reply: 4 (in socks5_recv_resolve_reply() at socks5.c:677) 1658731289 ERROR torsocks[21461]: Unable to resolve. Status reply: 4 (in socks5_recv_resolve_reply() at socks5.c:677) SMTP send failure: (550, b'No valid sender found in the From:, Sender: and Reply-to: headers'). You can retry, or save the report and exit. Do you want to retry [Y|n|q|?]? Connecting to reportbug.debian.org via SMTP... 1658731317 ERROR torsocks[21461]: Unable to resolve. Status reply: 4 (in socks5_recv_resolve_reply() at socks5.c:677) 1658731318 ERROR torsocks[21461]: Unable to resolve. Status reply: 4 (in socks5_recv_resolve_reply() at socks5.c:677) SMTP send failure: (550, b'No valid sender found in the From:, Sender: and Reply-to: headers'). You can retry, or save the report and exit. Do you want to retry [Y|n|q|?]? q ===8<------------------------------ Bug 1) It ignored the email address that was supplied in the saved draft and instead used the email address in the config file. When an email address is given for a specific bug report, that address should override the default address from the configs. Bug 2) Emacs was spawned to show me the bug report without me asking. Yet the prompt with option to edit (“E”) follows that anyway, and it defaults to E! The default “E” is reasonable if, and only if, the editor is not triggered before the prompt. So I had to override the default action and choose “y”. Bug 3) It says “Report is unchanged. Edit this report or quit [E|q|s|?]?” It’s accurate that the report is unchanged, but not interesting. The user should not be told that it was unchanged in a normal mode of execution. That should only appear if debugging reportbug with some extra verbosity. It’s particularly absurd that this prompt also defaults to “E”, as if to suggest that the input report /needs/ to be changed. It does not, and that’s not the normal course. This whole prompt should go away. Bug 4) It says “Sending empty report anyway...” and it does that without a prompt. So after the user receives excessive prompting, reportbug neglects to prompt to ask the user if it’s okay to send an empty report. The default action is also stupid. Why should reportbug even support the possibility of sending an empty report? That should never happen. Bug 5) The fact that reportbug *detects* the report as being empty is clearly a bug. It just showed me in the editor that my bug report was clearly not empty. It showed me a complete report, it knew I did not change that complete report, then it treats the report as empty. WTF. Bug 6) A backup report is saved which is an exact copy of the input report. Is there cause to think that the input file would be lost in this operation? In the case above, the backup file was saved in /tmp/ so the pollution will eventually be removed. But in other executions I’ve seen the backup report saved in my drafts directory -- the same directory that holds the input report. So there are multiple verbatim copies of the same report in that directory, thus pollution that persists. (note: some of the noise in the output sample is from torsocks, which can be ignored. Torsocks is used because of bug 880877) -- Package-specific info: ** Environment settings: EDITOR="emacs" INTERFACE="text" ** /home/blee/.reportbugrc: reportbug_version "7.10.3" mode advanced ui text realname "anonymous coward" email "foo@a5dbkgvakon2lxamlueiizkv6i3s36wpw3i32a63bu4xmtcnbdttmryd.onion" no-cc list-cc-me smtphost reportbug.debian.org -- System Information: Debian Release: 11.4 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-16-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+deb11u1 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+deb11u2 ii postfix [mail-transport-agent] 3.5.13-0+deb11u1 ii python3-urwid 2.1.2-1 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
