Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #168369
| From | Sven Hartge <sven@svenhartge.de> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: google-chrome-stable on Wheezy |
| Date | 2016-05-31 22:50 +0200 |
| Message-ID | <rEYLT-7qa-17@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <rEWqK-68v-27@gated-at.bofh.it> <rEWK5-6eV-1@gated-at.bofh.it> <rEWTN-6iC-53@gated-at.bofh.it> <rEXd7-6Ej-21@gated-at.bofh.it> <rEXwu-6KR-25@gated-at.bofh.it> |
| Organization | Newsfeed am Wurmloch |
Sven Joachim <svenjoac@gmx.de> wrote: > On 2016-05-31 21:03 +0200, Sven Hartge wrote: >> Ah, I see. Google compiled Chrome with a newer C++ library and broke >> the dependencies for Wheezy. >> I guess they waited until Wheezy was no longer supported by Debian >> outside of the LTS-Project and then dropped support for it. > No, Google does not care about Debian release cycles. The reason they > stopped supporting Wheezy is because they need a newer C++ compiler > and library with better C++11 support than offered by g++-4.7. OK, fair enough. >>> Seems I can not install google-chrome-stable on Wheezy anymore. >> >> Yes, seems that way. >> >> Only Chromium and Firefox remain. > Chromium in Wheezy was EOL'd 16 months ago, for the same reason that > there is no Google Chrome there: > https://lists.debian.org/debian-security-announce/2015/msg00031.html. Right, I misremembered and confused a different fact. Google at one time said it would not intentionally remove the support for 32bit architectures from the Chromium source, so that Distributions can still compile it. But this is of course not valid for Google Chrome. So the only remaining option for Wheezy is Firefox with Flash 11.2 (which is still supported by Adobe). Again: time to update. Grüße, Sven. -- Sigmentation fault. Core dumped.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
google-chrome-stable on Wheezy Mike McGinn <mikemcginn@mcginnweb.net> - 2016-05-31 19:40 +0200
Re: google-chrome-stable on Wheezy Lisi Reisz <lisi.reisz@gmail.com> - 2016-05-31 20:20 +0200
Re: google-chrome-stable on Wheezy Lisi Reisz <lisi.reisz@gmail.com> - 2016-05-31 20:20 +0200
Re: google-chrome-stable on Wheezy Sven Hartge <sven@svenhartge.de> - 2016-05-31 20:20 +0200
Re: google-chrome-stable on Wheezy Mike McGinn <mikemcginn@mcginnweb.net> - 2016-05-31 20:20 +0200
Re: google-chrome-stable on Wheezy Sven Hartge <sven@svenhartge.de> - 2016-05-31 20:40 +0200
Re: google-chrome-stable on Wheezy Mike McGinn <mikemcginn@mcginnweb.net> - 2016-05-31 20:50 +0200
Re: google-chrome-stable on Wheezy Sven Hartge <sven@svenhartge.de> - 2016-05-31 21:10 +0200
Re: google-chrome-stable on Wheezy conover@rahul.net (John Conover) - 2016-05-31 21:20 +0200
Re: google-chrome-stable on Wheezy Sven Hartge <sven@svenhartge.de> - 2016-05-31 22:40 +0200
Re: google-chrome-stable on Wheezy Sven Joachim <svenjoac@gmx.de> - 2016-05-31 21:30 +0200
Re: google-chrome-stable on Wheezy Sven Hartge <sven@svenhartge.de> - 2016-05-31 22:50 +0200
Re: google-chrome-stable on Wheezy Mike McGinn <mikemcginn@mcginnweb.net> - 2016-06-01 02:30 +0200
Re: google-chrome-stable on Wheezy SamuelOPH <samueloph@gmail.com> - 2016-06-01 05:20 +0200
Re: google-chrome-stable on Wheezy Mike McGinn <mikemcginn@mcginnweb.net> - 2016-06-01 11:50 +0200
Re: google-chrome-stable on Wheezy SamuelOPH <samueloph@gmail.com> - 2016-06-03 16:30 +0200
Re: google-chrome-stable on Wheezy Mike McGinn <mikemcginn@mcginnweb.net> - 2016-06-03 16:50 +0200
Re: google-chrome-stable on Wheezy Lisi Reisz <lisi.reisz@gmail.com> - 2016-06-03 18:40 +0200
Re: google-chrome-stable on Wheezy Lisi Reisz <lisi.reisz@gmail.com> - 2016-05-31 21:20 +0200
Re: google-chrome-stable on Wheezy Matthieu Méquignon <ml@fwzte.xyz> - 2016-05-31 20:20 +0200
csiph-web