chrome on f18 (fix)

[Patrick O'Callaghan]

On Wed, 2013-01-16 at 18:55 +0100, Reindl Harald wrote:
> 
> Am 16.01.2013 18:03, schrieb Neal Becker:
> > Mike Wohlgemuth wrote:
> > 
> >> On Wed, 2013-01-16 at 10:11 -0500, Neal Becker wrote:
> >>> Well, workaround really.
> >>>
> >>> /usr/lib64/libudev.so.0 -> /usr/lib64/libudev.so.1
> >>>
> >>
> >> A better solution is probably:
> >>
> >> yum remove google-chrome-stable
> >> yum install google-chrome-stable
> >>
> >> Woogie
> >>
> > 
> > Really?  I just tried it, but looks like google-chrome-stable is still linked to
> > libudev.so.0:
> > 
> > ldd /opt/google/chrome/chrome | grep udev
> >         libudev.so.0 => /lib64/libudev.so.0 (0x00007ff603cb0000)
> > 
> 
> for me it works, there must be some magic in the rpm-scripts
> 
> [root at srv-rhsoft:~]$ ldd /opt/google/chrome/chrome | grep udev
>         libudev.so.0 => not found
>         libudev.so.1 => /lib64/libudev.so.1 (0x00007fbd92d17000)
> 

I have the same results from ldd, but Chrome didn't work. I did the
remove/install with yum as above, and it did work.

I noticed that during the erase action, yum showed the repo as
"@google-chrome/17", but during the install it shows as "google-chrome".
The Chrome versions are exactly the same, so as you say there is clearly
some magic happening during the install which is different from F17 to
F18.

poc