Hi, Stephen Allen wrote: > On Tue, Apr 23, 2013 at 10:23:38PM -0400, Michael Gilbert wrote:
>> The bug was tagged "upstream" in your initial submission, which is >> supposed to mean that upstream is affected irregardless of whatever is >> in the debian package. Did you check this? > > Most likely. Does that mean "no"? If you can reproduce the bug using Google Chrome or by building the upstream sources for yourself, I don't think the chromium team will have any objections to receiving your report. ;-) Otherwise, you are facing the problem that the Debian chromium team receives many, many bug reports and doesn't have much time to deal with them. We might ask for your help in tracking down the problem further, for example by asking you to forward the report upstream (and you can blame us when talking to the chromium people in that case) or by asking you to test particular versions or patches. Thanks and hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
