#965085 reportbug: s to add x-debbugs-cc recipients is gone

#965085#5
Date:
2020-07-15 20:40:01 UTC
From:
To:
[…]
Report will be sent to Debian Bug Tracking System <submit@bugs.debian.org>
Submit this report on openssh-server (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|?]? s
Invalid selection.

#965085#10
Date:
2020-07-16 20:59:38 UTC
From:
To:
Thank you Thorsten for your report. The removal of this menu option is
not a bug; this was a deliberate decision. Two factors led to this:

 - Reportbug's MUA support has been significantly improved in the last
version, although with the limitation that custom headers cannot be
passed to all MUAs. Since that same menu offers an option to choose a
mailer for bug submission, we'd have had two options in the same menu
that interact very poorly.

 - There is an excellent alternative to setting an x-debbugs-cc header
-- you can set it as a pseudoheader. Just add a corresponding line to
the pseudoheader section of your report in the message editor. No
special UI or menu option is needed. The BTS supports x-debbugs-cc as
pseudoheader just fine. An additional benefit of doing it that way is
that recipients can immediately see why they received a copy.

So IMO there was no good reason any more to keep that menu option.
Further notes:

 - If you were used to adding an x-debbugs-cc to yourself for most bugs
you submit, you might want to check the list-cc-me (likely together with
no-cc) configuration options. This now also sets the x-debbugs-cc as a
pseudo-header, so you can edit it in the message editor.

 - Users still preferring to set this as a real header can use the
-H/--header command line option or the 'header' configuration directive,
or their own MUA's custom header facility if it has one. They should
avoid setting x-debbugs-cc as a pseudoheader in their messages too,
though, because I'm not sure both will be processed if both are present.

Hope this helps!

#965085#15
Date:
2020-07-16 21:44:31 UTC
From:
To:
Nis Martensen dixit:

… but I run reportbug only on systems where I have no MUA…

But that’s a lot to type and a weird string that invites typos.
(I mean, sure, I’ll probably make it, but consider other users.)

Does reportbug --configure expose this at least?

I did notice diverging behaviour between some systems; those
installed more recently put me on X-Debbugs-Cc, but not visibly
in the message.

I don’t really care about this header one way or the other, but
I’ve put me and other people involved on it for many bugs I sent
and am direly missing this feature.

So please bring it back.

Thanks,
//mirabilos


Michael Schmitz on nntp://news.gmane.org/gmane.linux.debian.ports.68k
a.k.a. {news.gmane.org/nntp}#news.gmane.linux.debian.ports.68k in pine

#965085#20
Date:
2020-07-17 18:43:55 UTC
From:
To:
If you enable the list-cc-me option, you don't have to type it. You'll
already have that line in the message editor and can add any additional
addresses you like.  I really recommend using that option.

It has been the default since November 2018, although only for users
without mta or custom smtphost; otherwise it is still commented out when
the configuration file is written.  We should possibly enable it for
everybody by default in new configuration files.

Older reportbug versions already used to set X-Debbugs-Cc via a 'header'
directive in the config file. This was changed to list-cc-me in 2018.

The visibility change was just implemented and uploaded a few days ago,
so it is not surprising if you haven't encountered it yet.

I'm quite convinced that this is not a good idea.

We'd have to add code to first identify any existing X-Debbugs-Cc
pseudoheader and then add the new recipient to it, or add a new line if
there isn't any. And we'd do this inside a message that was just edited
by the user anyway and that can easily be edited further.

If this were your developer time, would you want to spend it on that?

#965085#25
Date:
2020-07-17 21:02:09 UTC
From:
To:
Nis Martensen dixit:

Yes, of course.

Absolutely!

In addition to that, you probably should do that anyway and convert
between headers and pseudoheaders, so that only one is given, since
you said giving both can lead to unexpected results, so the software
really ought to prevent people from doing that.

bye,
//mirabilos

#965085#30
Date:
2020-07-17 21:12:23 UTC
From:
To:
Looking forward to receiving your patches :)
#965085#35
Date:
2020-07-17 21:42:04 UTC
From:
To:
Nis Martensen dixit:

$ file /usr/bin/reportbug
/usr/bin/reportbug: Python script, ASCII text executable


No, thanks.

bye,
//mirabilos

#965085#40
Date:
2020-07-17 23:26:56 UTC
From:
To:
Nis Martensen dixit:

Ah, if I re-run reportbug --configure, I get asked the same
questions as usual (and can just confirm), but the configuration
file written has different entries.

And with that, the bugreport in $EDITOR has an X-Debbugs-Cc: line,
already including myself, and which I just need to amend with more
addresses.

That counts as usable workaround until the, necessary due to other
reasons as outlined, fix is ready. Only thing going to confuse me
now is that only bullseye/sid systems will have this, not the others…

Thanks,
//mirabilos

#965085#47
Date:
2026-10-22 04:15:42 UTC
From:
To:
Hi,

as Nis explained back in 2020, the `s` option was removed on purpose in
7.7.0: X-Debbugs-Cc is now written as a pseudo-header in the report, so
it also survives when the report is handed to a mail client, and a
separate menu entry for it would interact badly with the mailer choice
in the same menu.

To add recipients you can:
 - enable list-cc-me (in ~/.reportbugrc, or --list-cc-me), so the report
   opens with an X-Debbugs-Cc: line with your address that you can extend;
 - pass --list-cc=ADDRESS on the command line;
 - in advanced or expert mode, answer the "additional addresses" prompt
   at the start.

The menu option won't come back, so I'm closing this.

Regards,
Sandro