Your message dated Mon, 27 Nov 2023 15:15:42 -0500
with message-id <6mts4s.bekp96597c...@queued.net>
and subject line Re: reportbug: http://www.crbug.com
has caused the Debian Bug report #1056621,
regarding reportbug: http://www.crbug.com
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 ow...@bugs.debian.org
immediately.)


-- 
1056621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 12.0.0
Severity: serious
Justification: Please do not redirect bugs to third party sites

Dear Maintainer,

pkg chromium is redirecting bugs through reportbug to http://www.crbug.com
$ apt policy chromium
chromium:
  Installed: 119.0.6045.159-1~deb12u1

I do not appreciate this.

thanks,
bw

-- Package-specific info:
** Environment settings:
INTERFACE="text"

** /home/user/.reportbugrc:
reportbug_version "7.1.7"
mode standard
ui text
email "bwtn...@yahoo.com"
no-cc
smtphost reportbug.debian.org

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

Kernel: Linux 6.5.0-0.deb12.1-amd64 (SMP w/8 CPU threads; PREEMPT)
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.6.1
ii  python3            3.11.2-1+b1
ii  python3-reportbug  12.0.0
ii  sensible-utils     0.0.17+nmu1

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail                                 <none>
ii  debconf                                    1.5.82
pn  debsums                                    <none>
pn  dlocate                                    <none>
pn  emacs-bin-common                           <none>
ii  exim4-daemon-light [mail-transport-agent]  4.96-15+deb12u2
ii  file                                       1:5.44-3
ii  gnupg                                      2.2.40-1.1
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.6.1
ii  file               1:5.44-3
ii  python3            3.11.2-1+b1
ii  python3-apt        2.6.0
ii  python3-debian     0.1.49
ii  python3-debianbts  4.0.1
ii  python3-requests   2.28.1+dfsg-1
ii  sensible-utils     0.0.17+nmu1

python3-reportbug suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- On Thu, 23 Nov 2023 17:19:30 -0500 debian user <bwtn...@yahoo.com> wrote:
> Package: reportbug
> Version: 12.0.0
> Severity: serious
> Justification: Please do not redirect bugs to third party sites
>
> Dear Maintainer,
>
> pkg chromium is redirecting bugs through reportbug to http://www.crbug.com
> $ apt policy chromium
> chromium:
>   Installed: 119.0.6045.159-1~deb12u1
>
> I do not appreciate this.
>
> thanks,


If you have suggestions for new wording for /usr/share/bug/chromium/presubj , I'm all ears.

Otherwise, this is
a) not an RC bug,
b) arguably not a bug at all, since it's simply text suggesting people use upstream's bug tracker instead of littering debian's bug tracking system with bugs that will never get looked at (see other browsers in debian for examples of that). Bug reporters can always decide to simply not do that.

A perfect example of this is <https://bugs.debian.org/1037232>. Jordan reported a valid bug to the debian BTS, which is fine, but I don't personally know the first thing about screen readers and Orca. They first reported the bug to upstream via crbug.com, provided upstream with a bunch of in-depth information and knowledge that I simply don't have, and have gotten the attention of chromium and igalia employees/developers.

Had they simply reported the bug to debian, assuming I had free time to look into it (which is a big assumption), I would've had to ask a bunch of questions of the submitter to get relevant information so that I could file a bug upstream. The reporter saved everyone time by just reporting the bug upstream first.
--- End Message ---

Reply via email to