[Secure-testing-team] Bug#857263: debian-maintainers: Hostility and failure to properly maintain Chromium package by Michael Gilbert

Loreno Heer helohe at bluewin.ch
Thu Mar 9 10:26:12 UTC 2017


Package: debian-maintainers
Severity: serious
Tags: security
Justification: Policy 4.3

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation? The maintainer disabled external extensions
for chromium / automatic extension updates. There is no easy way for the end
user to know what is going on or to solve the problem. The maintainer refuses
to fix this change. There are already several reports in the internet on forums
and blogs that the maintainer neglects the proper maintainance of the chromium
package. Several users decided therefore to no longer use it.
   * What exactly did you do (or not do) that was effective (or
     ineffective)? Reported a bug report as did many others but it is refused
to change it.
   * What was the outcome of this action?
   * What outcome did you expect instead? The package should conform to the
original functionality. Functionality should not be changed as per policy and
if a change is necessary it should be changed upstream.

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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



More information about the Secure-testing-team mailing list