Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1018101 > unrolled thread

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

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#965085: reportbug: s to add x-debbugs-cc recipients is gone Thorsten Glaser <tg@mirbsd.de> - 2020-07-15 23:00 +0200
    Bug#965085: reportbug: s to add x-debbugs-cc recipients is gone Nis Martensen <nis.martensen@web.de> - 2020-07-16 23:10 +0200
      Bug#965085: reportbug: s to add x-debbugs-cc recipients is gone Thorsten Glaser <tg@mirbsd.de> - 2020-07-17 00:00 +0200
        Bug#965085: reportbug: s to add x-debbugs-cc recipients is gone Nis Martensen <nis.martensen@web.de> - 2020-07-17 20:50 +0200
          Bug#965085: reportbug: s to add x-debbugs-cc recipients is gone Thorsten Glaser <tg@mirbsd.de> - 2020-07-17 23:10 +0200
            Bug#965085: reportbug: s to add x-debbugs-cc recipients is gone Nis Martensen <nis.martensen@web.de> - 2020-07-17 23:20 +0200
              Bug#965085: reportbug: s to add x-debbugs-cc recipients is gone Thorsten Glaser <tg@mirbsd.de> - 2020-07-17 23:50 +0200
          Bug#965085: reportbug: s to add x-debbugs-cc recipients is gone Thorsten Glaser <tg@mirbsd.de> - 2020-07-18 01:40 +0200

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

Package: reportbug
Version: 7.7.0
Severity: normal

[…]
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.

-- Package-specific info:
** Environment settings:
EDITOR="/usr/bin/sensible-editor"
VISUAL="/usr/bin/jupp"
DEBEMAIL="Thorsten Glaser <tg@mirbsd.de>"
INTERFACE="text"

** /home/tglase/.reportbugrc:
reportbug_version "6.6.6"
mode advanced
ui text

-- System Information:
Debian Release: bullseye/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), (100, 'experimental')
Architecture: x32 (x86_64)
Foreign Architectures: i386, amd64

Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages reportbug depends on:
ii  apt                2.1.7
ii  python3            3.8.2-3
ii  python3-reportbug  7.7.0
ii  sensible-utils     0.0.12+nmu1

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail                      <none>
ii  debconf-utils                   1.5.74
ii  debsums                         3.0.0
pn  dlocate                         <none>
pn  emacs-bin-common                <none>
ii  file                            1:5.38-5
ii  gnupg                           2.2.20-1
ii  postfix [mail-transport-agent]  3.5.4-1
pn  python3-urwid                   <none>
pn  reportbug-gtk                   <none>
ii  xdg-utils                       1.1.3-2

Versions of packages python3-reportbug depends on:
ii  apt                2.1.7
ii  file               1:5.38-5
ii  python3            3.8.2-3
ii  python3-apt        2.1.3
ii  python3-debian     0.1.37
ii  python3-debianbts  3.0.2
ii  python3-requests   2.23.0+dfsg-2
ii  sensible-utils     0.0.12+nmu1

python3-reportbug suggests no packages.

-- no debconf information

[toc] | [next] | [standalone]

#1018239

On Wed, 15 Jul 2020 Thorsten Glaser wrote:
> 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.

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!

[toc] | [prev] | [next] | [standalone]

#1018246

Nis Martensen dixit:

> - Reportbug's MUA support has been significantly improved in the last

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

> - 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

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.)

> - 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.

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.

> - Users still preferring to set this as a real header can use the

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
-- 
> Wish I had pine to hand :-( I'll give lynx a try, thanks.

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

[toc] | [prev] | [next] | [standalone]

#1018367

On 16.07.2020 23.44, Thorsten Glaser wrote:
> Nis Martensen dixit:
> 
>> - 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
> 
> 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.)

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.

>> - 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.
> 
> Does reportbug --configure expose this at least?

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.

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

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.

> So please bring it back.

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?

[toc] | [prev] | [next] | [standalone]

#1018379

Nis Martensen dixit:

>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

Yes, of course.

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

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
-- 
„Cool, /usr/share/doc/mksh/examples/uhr.gz ist ja ein Grund,
mksh auf jedem System zu installieren.“
	-- XTaran auf der OpenRheinRuhr, ganz begeistert
(EN: “[…]uhr.gz is a reason to install mksh on every system.”)

[toc] | [prev] | [next] | [standalone]

#1018381

On 17.07.2020 23.02, Thorsten Glaser wrote:
> Nis Martensen dixit:
>> If this were your developer time, would you want to spend it on that?
> 
> 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.

Looking forward to receiving your patches :)

[toc] | [prev] | [next] | [standalone]

#1018387

Nis Martensen dixit:

>Looking forward to receiving your patches :)

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


No, thanks.

bye,
//mirabilos
-- 
FWIW, I'm quite impressed with mksh interactively. I thought it was much
*much* more bare bones. But it turns out it beats the living hell out of
ksh93 in that respect. I'd even consider it for my daily use if I hadn't
wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh

[toc] | [prev] | [next] | [standalone]

#1018394

Control: severity -1 wishlist
Control: thanks

Nis Martensen dixit:

>> Does reportbug --configure expose this at least?
>
>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

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
-- 
15:39⎜«mika:#grml» mira|AO: "mit XFree86® wär’ das nicht passiert" - muhaha
15:48⎜<thkoehler:#grml> also warum machen die xorg Jungs eigentlich alles
kaputt? :)    15:49⎜<novoid:#grml> thkoehler: weil sie als Kinder nie den
gebauten Turm selber umschmeissen durften?	-- ~/.Xmodmap wonders…

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web