Your message dated Tue, 13 Oct 2015 06:40:22 +0100
with message-id 
and subject line Re: Bug#801545: reportbug picks debian-backports submission 
address inappropriately
has caused the Debian Bug report #801545,
regarding reportbug picks debian-backports submission address inappropriately
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Package: reportbug
Version: 6.6.3
Severity: normal

When filing # I had to manually save a draft and send the message via
mutt to fix the incorrect submission address of

The bug appears both in the version of libreoffice in stable and
in backports.

I manually corrected the Version: to reflect that the bug was
present in stable, but it appears that reportbug either picked this
address based on the version of the installed package, or is picking
up the bpo versions from the 'installed packages' section. Either way,
it's unhelpful behaviour.

Thanks for maintaining reportbug and let me know if you need any more
infomation to fix this.


-- Package-specific info:
** Environment settings:

** /home/dom/.reportbugrc:
reportbug_version "6.6.3"
mode advanced
ui text

-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages reportbug depends on:
ii  apt     
ii  python            2.7.9-1
ii  python-reportbug  6.6.3
pn  python:any        <none>

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail                                 <none>
pn  debconf-utils                              <none>
pn  debsums                                    <none>
pn  dlocate                                    <none>
pn  emacs23-bin-common | emacs24-bin-common    <none>
ii  exim4                                      4.84-8
ii  exim4-daemon-light [mail-transport-agent]  4.84-8
ii  file                                       1:5.22+15-2
ii  gnupg                                      1.4.18-7
ii  python-gtk2                                2.24.0-4
pn  python-gtkspell                            <none>
pn  python-urwid                               <none>
pn  python-vte                                 <none>
ii  xdg-utils                                  1.1.0~rc1+git20111210-7.4

Versions of packages python-reportbug depends on:
ii  apt     
ii  python-debian     0.1.27
ii  python-debianbts  1.12
pn  python:any        <none>

python-reportbug suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
> The problem is that from a user experience point of view, the
> problem isn't discovered until after all the hard work of writing
> the bug report is done.

from a user perspective, they should just trust the program. from a
developer perspective, it's expected to be able to change the program
behavior to match what they are doing, if that's not the usual

> Anyway, I don't think we're really getting anywhere, so this is the
> last from me on this bug.

alright, closing then (as in I'm not going to change the behavior of
reportbug for this)

Sandro Tosi (aka morph, morpheus, matrixhasu)
My website:
Me at Debian:

--- End Message ---
Reportbug-maint mailing list

Reply via email to