Had LSB problem, now have /usr/bin conflict problem

jbruyet · 09-21-2014, 11:19 PM

Hey all, I'm trying to install Google Earth on a fresh install of CentOS 7:

Code:

 rpm -ivh google-earth-stable_current_x86_64.rpm

I was getting an error message that LSB needed to be >3.2 so I ran:

Code:

 yum install redhat-lsb-core.x86_64

I was still getting the error so next I ran:

Code:

yum install redhat-lsb.x86_64

That took care of the LSB error but now when I run the Google Earth install I get this error:

Code:

 file /usr/bin from install of google-earth-stable-7.1.2.2041-0.x86_64 conflicts with file from package filesystem-3.2-18.el7.x86_64

Googling this error gives me one hit: https://forums.nux.ro/index.php?t=msg&goto=2137&

The recommendation on that page is to run:

Code:

 yum install redhat-lsb.i686

and then reinstall Google Earth. I'm hesitant to mix an i686 install with an x86_64 install. Should I run the i686 install for the lsb or should I look elsewhere?

Thanks,

Joe B

unSpawn · 10-12-2014, 05:05 AM

Quote:

Originally Posted by jbruyet

Code:

 file /usr/bin from install of google-earth-stable-7.1.2.2041-0.x86_64 conflicts with file from package filesystem-3.2-18.el7.x86_64

(..) I'm hesitant to mix an i686 install with an x86_64 install. Should I run the i686 install for the lsb or should I look elsewhere?

And right you are. The problem isn't your OS or your LSB %{arch} or %{version} but the sheer boneheaded stubbornness and utter ineptitude of those packaging Google Earth. Google packagers violated a basic packaging rule by choosing to include the directory "/usr/bin" in their package that belongs to the system and not to Google Earth. And even though people have asked Google to comply it, to this day, has not which means they basically don't care. Damn sloppy.

Long story short: three ways to "fix" this:
0) download RPM, verify contents, unpack ('man rpm2cpio') into dir in say /opt, run 'restorecon', query package with "--scripts" and execute appropriate %{post} section. Please note this causes discrepancies because now you have files on your installation that do not belong to any package, meaning you bear the burden of updating it manually, but at least this doesn't tarnish your "filesystem" package.
1) download RPM, verify contents, unpack ('man rpm2cpio') into temporary dir, query package with "--scripts" for appropriate %{post} section, create your own package and install that. Please note this also causes discrepancies because now you have a package that does not belong to any repo, meaning you still bear the burden of updating it manually, but at least this doesn't tarnish your "filesystem" package.
2) Force to install google-earth-stable, then force to install filesystem package again. Please note use of --force should always be discouraged and for good reasons.

*Oddly enough the google-earth-stable-7.1.2.2041-0.i386 RPM doesn't seem to include the "/usr/bin" directory in that package so I wonder what's gone wrong at Google...