On Wed, 3 Jul 2013, Steven Haigh wrote:

> On 3/07/2013 6:04 PM, Yasha Karant wrote:
>>  On 07/02/2013 04:47 PM, Steven Haigh wrote:
>> >  On 3/07/2013 9:33 AM, Tam Nguyen wrote:
>> > >  On Tue, Jul 2, 2013 at 6:45 PM, Yasha Karant <[log in to unmask]
>> > > >  <mailto:[log in to unmask]>> wrote:
>> > > > 
>> > > >      Add/remove software shows:
>> > > > 
>> > > >      google-chrome-stable-28.0.__1500.70-209565 (x86_64)
>> > > > 
>> > > >      but installation results in a transaction error:
>> > > > 
>> > > >      google-chrome-stable-28.0.__1500.70-209565.x86_64 requires
>> > > >      libstdc++.so.6(GLIBCXX_3.4.15)__(64bit)
>> > > > 
>> > > >      and the dependency does not automatically resolve.  Is there a
>> > > >      workaround for this
>> > > >      issue?
>> > > 
>> > >  Download Google rpm here: http://orion.lcg.ufrj.br/RPMS/myrpms/google/
>> > >  then yum install the download rpm.
>> > 
>> >  Sorry - but I think its really bad practice to just refer people to
>> >  random, unknown repositories for common software...
>> > 
>> >  In a nutshell, the version of libstdc++ seems to be rather old that
>> >  Google are using. SL has:
>> > 
>> >  # yum whatprovides libstdc++.so.6
>> >  libstdc++-4.4.7-3.el6.i686 : GNU Standard C++ Library
>> >  Repo        : sl6x
>> >  Matched from:
>> >  Other       : libstdc++.so.6
>> > 
>> >  I'd recommend is using chromium if you don't rely on any Google-only
>> >  features.
>> > 
>> >  There is a thread about this on the SL forums:
>> >       http://scientificlinuxforum.org/index.php?showtopic=1134
>> > 
>>
>>  I thoroughly am confused about these responses.  Unless I am mistaken,
>>  the chrome RPM seems to be from a standard EL6 repository.  Moreover,
>>  the previous release of chrome through this same method did not produce
>>  this error, and installed and ran without obvious issues.  However, as
>>  updates typically both fix bugs and security holes, we routinely update
>>  to current production.  It is only the most current release of "real"
>>  chrome (not chromium) that shows this problem -- is there a repository
>>  with the necessary RPMs for a proper workaround?
>
> Google calls RHEL6 'too old' and 'obsolete' now. See:
> http://linux.slashdot.org/story/13/02/11/1452259/rhel-6-no-longer-supported-by-google-chrome
>
> Nothing in EL6 caused this break - purely internal stuff from Google.

Their build-system is Ubuntu based, and Ubuntu moved on.

It's pretty cynical to learn that at Google the RHEL packages have been 
build in an Ubuntu environment, rather than properly packaged on the same 
distribution. A practice that almost everyone is doing today.

It's amazing that this even worked, we'd be better off if it didn't...

-- 
-- dag wieers, [log in to unmask], http://dag.wieers.com/
-- dagit linux solutions, [log in to unmask], http://dagit.net/

[Any errors in spelling, tact or fact are transmission errors]