Bug#988391: reportbug: X-Debbugs-CC problems
Package: reportbug
Version: 7.10.3
Severity: normal
X-Debbugs-Cc: RossBoylan@stanfordalumni.org
Dear Maintainer,
* What led up to the situation?
<terminal>
ross@debtest:~$ reportbug logcheck-database -H 'X-Debbugs-CC: 987839@bugs.debian.org'
*** Warning: Your ~/.reportbugrc is setting an X-Debbugs-CC header in a 'header' command. This is an old default setting that no longer works reliably. You may
want to re-run 'reportbug --configure', or edit your configuration file to use the 'list-cc-me' command (without recipient address) instead.
*** Welcome to reportbug. Use ? for help at prompts. ***
</terminal>
Then when the editor spawned I did not see X-Debbugs-CC in the
file, although I do see it for this bug, which used --list-cc-me.
Read documentation and got confused abut how different ways of
specifying X-Debbugs-CC interacted.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I ignored the warning and filed the report without being able to
add myself to the X-Debbugs-CC list.
* What was the outcome of this action?
Bug submitted and the message was cc'd to me (before getting a bug
# assigned). The cc surprised me, but I presume it's the result of
/etc/reportbug.conf having a cc directive.
* What outcome did you expect instead?
1. That the error message would be accurate. It said
*** Warning: Your ~/.reportbugrc is setting an X-Debbugs-CC header in a 'header' command. .....
My .reportbugrc has no header or debbugs-cc related directives. I
assume the warning was triggered by the -H option on the command
line.
Also, the warning message went on to suggest --list-cc-me,
which was not appropriate since the edress I gave was not me.
2. That there would be some way to edit my X-Debbugs-CC list after
the fact. I realized after I started that I wanted to include
myself in list, and had no way to do it (unless I overlooked an
X-Debbugs-CC line in the editor). I could have added such a line
in the editor, but it was unclear how that would interact with the
previous request from the command line.
Related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648185
3. That I would be able to figure out how different header-related
options interacted from t he documentation.
In general, there are multiple ways to set the X-Debbugs-CC list, and
it is unclear how they interact. For example, what if I have
list-cc-me and an explicit X-Debbugs-CC header? If there are several
such headers, what happens?
https://www.debian.org/Bugs/Reporting#pseudoheader says
If you want to send copies to more than one address, add them
comma-separated in only one X-Debbugs-CC line.
<aside>
Oops, I guess I shouldn't have done an X-Debbugs-CC to another bug,
because it continues
Avoid sending such copies to the addresses of other bug
reports, as they will be caught by the checks that prevent mail
loops. There is relatively little point in using X-Debbugs-CC for this
anyway, as the bug number added by that mechanism will just be
replaced by a new one; use an ordinary CC header instead.
</aside>
The man page has both -P and -H. What's the difference? How do they
interact with -list-cc or --list-cc-me, or options set in
configuration files?
-H describes how to set X-Debbugs-CC, but
--list-cc=ADDRESS
Send a carbon copy of the report to the specified list after a report
number is assigned; this is the equivalent to the option -P
'X-Debbugs-CC: ADDRESS'. This option will only work as intended with
debbugs systems.
uses -P instead.
-- Package-specific info:
** Environment settings:
INTERFACE="text"
** /home/ross/.reportbugrc:
reportbug_version "7.10.3"
mode standard
ui text
email "RossBoylan@stanfordalumni.org"
smtphost "mail.betterworld.us"
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-6-amd64 (SMP w/3 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages reportbug depends on:
ii apt 2.2.3
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>
ii debsums 3.0.2
pn dlocate <none>
ii emacs-bin-common 1:27.1+1-3.1
ii exim4-daemon-light [mail-transport-agent] 4.94-17
ii file 1:5.39-3
ii gnupg 2.2.27-2
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.3
ii file 1:5.39-3
ii python3 3.9.2-3
ii python3-apt 2.2.0
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: