chromium now depends on gconf + wtf is payment methods?

[bw123]

wtf, this is getting out of hand? Why do I need gconf to use chromium? Isn't gconf deprecated? Why is this not mentioned in the changelog?

Security upgrades are great, enabling new crap under the radar like 'payment methods' is not cool.

Code: Select all

$ apt policy chromium
chromium:
  Installed: 70.0.3538.67-1~deb9u1
  Candidate: 70.0.3538.67-1~deb9u1
  Version table:
 *** 70.0.3538.67-1~deb9u1 500
        500 http://security.debian.org stretch/updates/main amd64 Packages
        100 /var/lib/dpkg/status
     63.0.3239.84-1~deb9u1 500
        500 http://deb.debian.org/debian stretch/main amd64 Packages


p.s. I caught the other thing too, you bastard.

[Head_on_a_Stick]

Why do I need gconf to use chromium?

No idea but my buster box doesn't seem to need it:

Code: Select all

empty@buster:~ $ apt policy gconf-service chromium                                 
gconf-service:
  Installed: (none)
  Candidate: 3.2.6-5
  Version table:
     3.2.6-5 500
        100 https://cdn-aws.deb.debian.org/debian sid/main amd64 Packages
        500 https://cdn-aws.deb.debian.org/debian buster/main amd64 Packages
chromium:
  Installed: 70.0.3538.67-2
  Candidate: 70.0.3538.67-2
  Version table:
 *** 70.0.3538.67-2 500
        100 https://cdn-aws.deb.debian.org/debian sid/main amd64 Packages
        500 https://cdn-aws.deb.debian.org/debian buster/main amd64 Packages
        100 /var/lib/dpkg/status
empty@buster:~ $

I think FF (esr) is better supported in Debian though, it seems to receive updates quicker than the chromium package.

p.s. I caught the other thing too, you bastard.

D00d you are a class act.

[stevepusser]

Apparently that dependency was removed in the -2 rebuild.

Code: Select all

chromium-browser (70.0.3538.67-2) unstable; urgency=medium

  * Restore support for building with gtk2.

 -- Michael Gilbert <mgilbert@debian.org>  Tue, 23 Oct 2018 01:11:35 +0000

chromium-browser (70.0.3538.67-1) unstable; urgency=medium