Medibuntu

Googleearth installs version 4.2 in Hardy, not 4.3

Asked by Larry Trickey

After updating repositories as described on the Medibuntu's web page ( using wget ) into a fresh installation of Hardy 8.04 , I installed googleearth using "sudo apt-get install googleearth", I ended up with version 4.2 installed. Immediately running the program suggests an update is available,and but it works(I declined the update). After checking in Synaptic, it shows a 4.2 and 4.3 version, but synaptic doesn't offer to upgrade. After installing the 4.3 version by marking it manually in Synaptic, it installs. However,after the upgrade clicking on the launcher does nothing...though there might be a error message sent somewhere...I don't know.

 I then purged all Googleearth packages and installed using the binary from Google ( which turned out to be version 4.3.7204.836 with permission and ownership problems). I'd rather use your repository though.

I did notice the same happened on my brothers system after he installed it into his Hardy Heron ( he got version 4.2 ).

Can you check the reversion control settings (however that is done?) for the package please?

P.S. Medibuntu is the only extra repository I've added

Question information

Language:
English Edit question
Status:
Solved
For:
Medibuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Larry Trickey
Solved:
Last query:
Last reply:
Revision history for this message
Lionel Le Folgoc (mrpouit) said : 		#1

Hi,

We did this on purpose, because googleearth 4.3 doesn't work on older cpus (prior to amd athlon 64 and pentium 4).

Cf. https://bugs.launchpad.net/medibuntu/+bug/220188

Revision history for this message
Larry Trickey (larrytrickey) said : 		#2

Everything makes sense when you know the answer...Thanks for explaining

Revision history for this message
Michael Lueck (mlueck) said : 		#3

I found you can add the 4.3 builds via Medibuntu / Synpatic just that you need to add the 4.3 package instead of the one without a version which will bring down its 4.2 dependencies.

This was a bit confusing to me as the package without a number in its name was version 4.3, but the dependencies were all 4.2 for that one. Thus I came looking to find out why that was, and it looks like I found the answer! :-)