Downloaded google-earth-stable_current_x86_64.rpm from google and tried to install it, got
# dnf install google-earth-stable_current_x86_64.rpm Last metadata expiration check performed 0:42:30 ago on Sun Feb 14 12:22:13 2016. Dependencies resolved. ================================================================================================================================================================ Package Arch Version Repository Size ================================================================================================================================================================ Installing: google-earth-stable x86_64 7.1.4.1529-0 @commandline 60 M
Transaction Summary ================================================================================================================================================================ Install 1 Package
Total size: 60 M Installed size: 194 M Is this ok [y/N]: y Downloading Packages: Running transaction check Transaction check succeeded. Running transaction test Error: Transaction check error: file /usr/bin from install of google-earth-stable-7.1.4.1529-0.x86_64 conflicts with file from package filesystem-3.2-32.fc22.x86_64
Error Summary -------------
================================================================================================================================================================
But I know how to fix the rpm.
On Sun, Feb 14, 2016 at 01:07:09PM -0700, jd1008 wrote:
Downloaded google-earth-stable_current_x86_64.rpm from google
Yeah, google messed up. They don't seem to care, it's been like that for quite some time.
If you can find the right forum at google, there is a loooooong thread on problem with the linux version of google earth, and one of the things it tells is how to fix the RPM using rpmrebuild. Once you get the RPM fixed so it will install, you may have a bunch of other problems with rendering imagery. that is discussed in that looooong thread also. Mostly it mentions Ubuntu, but there is a link to another thread that tells how to fix it on Fedora. I applied that on Centos 7 and now google earth works almost perfectly, or close enough to actually be usable.
I don't have links to those threads, but I can go look for them again if you get stuck.
Fred
and tried to install it, got
# dnf install google-earth-stable_current_x86_64.rpm Last metadata expiration check performed 0:42:30 ago on Sun Feb 14 12:22:13 2016. Dependencies resolved. ================================================================================================================================================================ Package Arch Version Repository Size ================================================================================================================================================================ Installing: google-earth-stable x86_64 7.1.4.1529-0 @commandline 60 M
Transaction Summary
Install 1 Package
Total size: 60 M Installed size: 194 M Is this ok [y/N]: y Downloading Packages: Running transaction check Transaction check succeeded. Running transaction test Error: Transaction check error: file /usr/bin from install of google-earth-stable-7.1.4.1529-0.x86_64 conflicts with file from package filesystem-3.2-32.fc22.x86_64
Error Summary
================================================================================================================================================================
But I know how to fix the rpm.
users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 02/14/2016 06:56 PM, Fred Smith wrote:
On Sun, Feb 14, 2016 at 01:07:09PM -0700, jd1008 wrote:
Downloaded google-earth-stable_current_x86_64.rpm from google
Yeah, google messed up. They don't seem to care, it's been like that for quite some time.
If you can find the right forum at google, there is a loooooong thread on problem with the linux version of google earth, and one of the things it tells is how to fix the RPM using rpmrebuild. Once you get the RPM fixed so it will install, you may have a bunch of other problems with rendering imagery. that is discussed in that looooong thread also. Mostly it mentions Ubuntu, but there is a link to another thread that tells how to fix it on Fedora. I applied that on Centos 7 and now google earth works almost perfectly, or close enough to actually be usable.
I don't have links to those threads, but I can go look for them again if you get stuck.
Fred
Already fixed hours ago. I am having no issues with rendering - just slow.
On Sun, Feb 14, 2016 at 07:03:07PM -0700, jd1008 wrote:
On 02/14/2016 06:56 PM, Fred Smith wrote:
On Sun, Feb 14, 2016 at 01:07:09PM -0700, jd1008 wrote:
Downloaded google-earth-stable_current_x86_64.rpm from google
Yeah, google messed up. They don't seem to care, it's been like that for quite some time.
If you can find the right forum at google, there is a loooooong thread on problem with the linux version of google earth, and one of the things it tells is how to fix the RPM using rpmrebuild. Once you get the RPM fixed so it will install, you may have a bunch of other problems with rendering imagery. that is discussed in that looooong thread also. Mostly it mentions Ubuntu, but there is a link to another thread that tells how to fix it on Fedora. I applied that on Centos 7 and now google earth works almost perfectly, or close enough to actually be usable.
I don't have links to those threads, but I can go look for them again if you get stuck.
Fred
Already fixed hours ago. I am having no issues with rendering - just slow.
cool! Just curious what Fedora version are you using?
On 02/14/2016 07:08 PM, Fred Smith wrote:
On Sun, Feb 14, 2016 at 07:03:07PM -0700, jd1008 wrote:
On 02/14/2016 06:56 PM, Fred Smith wrote:
On Sun, Feb 14, 2016 at 01:07:09PM -0700, jd1008 wrote:
Downloaded google-earth-stable_current_x86_64.rpm from google
Yeah, google messed up. They don't seem to care, it's been like that for quite some time.
If you can find the right forum at google, there is a loooooong thread on problem with the linux version of google earth, and one of the things it tells is how to fix the RPM using rpmrebuild. Once you get the RPM fixed so it will install, you may have a bunch of other problems with rendering imagery. that is discussed in that looooong thread also. Mostly it mentions Ubuntu, but there is a link to another thread that tells how to fix it on Fedora. I applied that on Centos 7 and now google earth works almost perfectly, or close enough to actually be usable.
I don't have links to those threads, but I can go look for them again if you get stuck.
Fred
Already fixed hours ago. I am having no issues with rendering - just slow.
cool! Just curious what Fedora version are you using?
FC22 with latest updates.
On Sun, 14 Feb 2016 20:56:33 -0500 Fred Smith wrote:
Yeah, google messed up. They don't seem to care, it's been like that for quite some time.
As near as I can tell the lunatic paranoia about not allowing more than one package to "own" a directory is entirely in the head of dnf/yum. Last time I tried doing a rpm -i works fine on such packages.
jd1008 wrote:
Downloaded google-earth-stable_current_x86_64.rpm from google and tried to install it, got
Error: Transaction check error: file /usr/bin from install of google-earth-stable-7.1.4.1529-0.x86_64 conflicts with file from package filesystem-3.2-32.fc22.x86_64
google has been made aware of that packaging bug for quite awhile now, but they seem to have yet to fix it.
-- Rex
On 02/15/2016 07:04 AM, Rex Dieter wrote:
jd1008 wrote:
Downloaded google-earth-stable_current_x86_64.rpm from google and tried to install it, got Error: Transaction check error: file /usr/bin from install of google-earth-stable-7.1.4.1529-0.x86_64 conflicts with file from package filesystem-3.2-32.fc22.x86_64
google has been made aware of that packaging bug for quite awhile now, but they seem to have yet to fix it.
-- Rex
And the fix is so totally simple. Just remove one line from the spec file: %dir %attr(0755, root, root) "/usr/bin" which is line 341
Quoting jd1008 jd1008@gmail.com:
On 02/15/2016 07:04 AM, Rex Dieter wrote:
jd1008 wrote:
Downloaded google-earth-stable_current_x86_64.rpm from google and tried to install it, got Error: Transaction check error: file /usr/bin from install of google-earth-stable-7.1.4.1529-0.x86_64 conflicts with file from package filesystem-3.2-32.fc22.x86_64
google has been made aware of that packaging bug for quite awhile now, but they seem to have yet to fix it.
-- Rex
And the fix is so totally simple. Just remove one line from the spec file: %dir %attr(0755, root, root) "/usr/bin" which is line 341
that's very useful and leaves me totally agog wondering how you found it - exhaustive search?? or what??
Dave
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
jd1008:
And the fix is so totally simple. Just remove one line from the spec file: %dir %attr(0755, root, root) "/usr/bin" which is line 341
Dave Stevens:
that's very useful and leaves me totally agog wondering how you found it - exhaustive search?? or what??
What's more mind-boggling is why those (in Google) who created the problem haven't pulled their fingers out and fixed it. It's not a new problem, the fault is entirely theirs, and they should know better. Don't make the users jump through hoops to fix things that you've broken.
On 02/15/2016 11:44 AM, Tom Horsley wrote:
Actually it is a new problem. Yum was fine with multiple rpms defining the same directory till somewhere around fedora 19 or 20, then it suddenly became an error.
I first ran into it when I upgraded from Fedora 19 to 20, suggesting that it started with F 20.
Tom Horsley wrote:
On Tue, 16 Feb 2016 05:47:23 +1030 Tim wrote:
It's not a new problem
Actually it is a new problem. Yum was fine with multiple rpms defining the same directory till somewhere around fedora 19 or 20, then it suddenly became an error.
I don't think the problem is multiple rpm's simply defining the same directory; it's when they define the directory differently. Numerous packages own /etc/bash_completion.d and they don't fail to install with yum or dnf, for example.
The line quoted earlier from the google package set the mode to 755, while the filesystem package sets it to 555.
Tim:
It's not a new problem
Tom Horsley:
Actually it is a new problem. Yum was fine with multiple rpms defining the same directory till somewhere around fedora 19 or 20, then it suddenly became an error.
I don't think relying on the updating software not caring that you're trying to own a directory that you have no business owning, is a good practice. That's what I mean by not a new problem. Google Earth has made that mistake for years.
Applications should only try to own their own directories. If they depend on some system directories/files which may not be present, then they should be called in from either a system package, or be an optional install. Not try and jam in on top of existing paths and ownerships.
On 2/15/16, Tim ignored_mailbox@yahoo.com.au wrote:
What's more mind-boggling is why those (in Google) who created the problem haven't pulled their fingers out and fixed it. It's not a new problem, the fault is entirely theirs, and they should know better. Don't make the users jump through hoops to fix things that you've broken.
Decades ago when discussing why IBM divisions couldnt get behind their own OS (OS/2 Warp) it was said that at a giant corp like Big Blue "the right hand doesn't know what the left hand is doing".
That applies to all big corps, and in the case of Google, I suspect there must be a total disconnect between the development team and the outsourced keyboard punchers answering questions on "web forums".
What someone should do is look up what's the name of the Google Earth product manager, find him on Linkedin, and publiucly shame him. I mean surely he's getting paid really well for managing a product he's clearly not managing or cariung about very well.
I mean, if I had "Google Earth product manager @ Google" the least I'd do is ask for one machine with every OS suported, install "my product" on all of 'em and use them on a daily basis to make sure users are getting a consistent experience, then regularly roam the web support forums and see what the feedback about the product is, then discuss problems reported there with the devs.
That's clearly NOT happening.
I think by now Google is hopelessly in the "too big to fail" category. I mean, I just got a tiny ARM netbook that comes preloaded with Android Kitkat. Google Maps was part of the apps bundle. On the first update I let Google Play install, the Maps app became unusable.
Something surely having to do with a screen size adjustement setting... because as soon as the app is launched the screen enters a resizing frenzy o a loop,and you can't exit it. You have to turn off the system and reboot. Great work, Google, it shows your app testing is reaching new world records... ;)
FC
-
Dave Stevens -
Fernando Cassia -
Fred Smith -
JD -
Joe Zeff -
Rex Dieter -
Tim -
Todd Zullinger -
Tom Horsley