On Sun, Dec 13, 2015 at 03:00:05AM +0000, Debian Bug Tracking System wrote: > Date: Sat, 12 Dec 2015 21:57:18 -0500 > From: Michael Gilbert <mgilb...@debian.org> > To: 807785-cl...@bugs.debian.org > Subject: Re: Bug#807785: chromium: caches certificate chains > Message-ID: > <CANTw=moqm+sgzf8zpubtgufeffltggvkmz1lzg70o1uyzmw...@mail.gmail.com> > > On Sat, Dec 12, 2015 at 9:41 PM, brian m. carlson wrote: > > On Sat, Dec 12, 2015 at 09:20:13PM -0500, Michael Gilbert wrote: > >> control: tag -1 upstream > >> > >> Since this isn't a packaging issue, please report this upstream. > > > > Please feel free to forward it there. I report bugs to Debian so I > > don't have to have an account on every bug tracker on the planet. The > > upstream bug tracker also forces me to use my Gmail address, which I > > don't actually want to use. > > I have no interest in this problem. You're wasting my time if you're > not willing to to debug or sheppard it yourself.
With due respect, it's always been the job of the Debian maintainer of a package to forward bugs upstream. Oftentimes, a bug is due to a Debian-specific patch or dependency, in which case sending the bug report upstream is ineffective and just serves to irritate upstream. The Debian BTS is *the* right place to report bugs that are in Debian. For example, this behavior appears to be an interaction with NSS[0][1]. It was my understanding that Chromium 47 was supposed to use BoringSSL on Linux, but apparently Chromium in Debian is still linked against NSS, which may be related. [0] https://bugzilla.mozilla.org/show_bug.cgi?id=733232 [1] https://wiki.mozilla.org/NSS:BurnDownList, see "Stop caching intermediate certificates on disk" -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | https://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
signature.asc
Description: PGP signature
