You are not logged in.
Okay, so I am trying to install google earth on my crunchbang install. I downloaded the 32 bit deb package from the google website and tried running dpkg on it:
bruce@bruce:~/applications$ sudo dpkg -i googleearth.deb
(Reading database ... 134640 files and directories currently installed.)
Preparing to replace google-earth-stable 7.1.2.2041-r0 (using googleearth.deb) ...
Unpacking replacement google-earth-stable ...
dpkg: dependency problems prevent configuration of google-earth-stable:
google-earth-stable depends on lsb-core (>= 3.2).
dpkg: error processing google-earth-stable (--install):
dependency problems - leaving unconfigured
Processing triggers for man-db ...
Processing triggers for menu ...
Processing triggers for desktop-file-utils ...
Errors were encountered while processing:
google-earth-stableIn my synaptic package manager, I appear to have lsb-core installed, so I assumed that I needed the i386 version of that package.
But running apt-get, gets me
bruce@bruce:~/applications$ sudo apt-get install lsb-core:i386
[sudo] password for bruce:
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
lsb-core : Conflicts: lsb-core:i386 but 4.1+Debian8+deb7u1 is to be installed
lsb-core:i386 : Depends: libc6:i386 (> 2.3.5) but it is not going to be installed
Depends: libz1:i386
Depends: libncurses5:i386 but it is not going to be installed
Depends: libpam0g:i386 but it is not going to be installed
Depends: lsb-invalid-mta:i386 (>= 4.1+Debian8+deb7u1) but it is not installable or
mail-transport-agent:i386
Depends: bc:i386
Depends: binutils:i386 but it is not going to be installed
Depends: bsdmainutils:i386
Depends: cpio:i386
Depends: cron:i386 but it is not going to be installed or
cron-daemon:i386
Depends: ed:i386
Depends: libc6-dev:i386 but it is not going to be installed or
libc-dev:i386
Depends: locales:i386
Depends: mailutils:i386 but it is not going to be installed or
mailx:i386
Depends: make:i386
Depends: psmisc:i386
Depends: alien:i386 (>= 8.36) but it is not installable
Depends: python:i386 (>= 2.6.6-7~) but it is not going to be installed
Depends: lsb-security:i386 (>= 4.1+Debian8+deb7u1) but it is not going to be installed
Depends: time:i386 but it is not going to be installed
Conflicts: lsb-core but 4.1+Debian8+deb7u1 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
The first dpkg command worked fine on my kubuntu install once I had installed lsb-core from synaptic on there. Should I maybe add the repository my kubuntu install used for the lsb-core package?
Offline
Google Earth is available for GNU/Linux from their web site, but is non-free software and is undistributable. It also does not integrate well into a Debian system.
sudo aptitude install googleearth
Offline
Using 64-bit #!?
I'm pretty sure you still need to set up multiarch then build the googleearth deb package. There is a thread on this forum to do that properly for #!.
Last edited by PackRat (2014-09-12 22:03:40)
"It does not require many words to speak the truth." - Chief Joseph, Nez Perce tribe
Offline
Debian.org wrote:Google Earth is available for GNU/Linux from their web site, but is non-free software and is undistributable. It also does not integrate well into a Debian system.
sudo aptitude install googleearth
When I run that I get
bruce@bruce:~$ sudo aptitude install googleearth
No candidate version found for googleearth
No candidate version found for googleearth
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Is there a specific version name that needs to go in place of 'googleearth'?
Also, what is the difference between apt-get and aptitude
Offline
I think it's googleearth-package
"It does not require many words to speak the truth." - Chief Joseph, Nez Perce tribe
Offline
I think it's googleearth-package
Yup...
https://packages.debian.org/wheezy/googleearth-package
Also, what is the difference between apt-get and aptitude
http://crunchbang.org/forums/viewtopic. … 18#p394618
Last edited by Head_on_a_Stick (2014-09-12 22:09:20)
Offline
I think it's googleearth-package
Nope, still get the same output
Offline
^ Uh-oh...
Update your APT database:
sudo apt-get update& try again.
If it still doesn't find it, post your /etc/apt/sources.list & the output of:
apt-cache policyOffline
^ Uh-oh...
Update your APT database:sudo apt-get update& try again.
If it still doesn't find it, post your /etc/apt/sources.list & the output of:apt-cache policy
Tried the update, got
bruce@bruce:~$ sudo aptitude install googleearth-package
The following partially installed packages will be configured:
googleearth{b}
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
The following packages have unmet dependencies:
googleearth : Depends: ia32-libs-gtk but it is not going to be installed.
The following actions will resolve these dependencies:
Remove the following packages:
1) googleearth the content of sources.list is
## CRUNCHBANG
## Compatible with Debian Wheezy, but use at your own risk.
deb http://packages.crunchbang.org/waldorf waldorf main
# deb-src http://packages.crunchbang.org/waldorf waldorf main
## DEBIAN
deb http://http.debian.net/debian wheezy main contrib non-free
# deb-src http://http.debian.net/debian wheezy main contrib non-free
## DEBIAN SECURITY
deb http://security.debian.org/ wheezy/updates main
# deb-src http://security.debian.org/ wheezy/updates main
deb http://ftp.de.debian.org/debian jessie main
# deb http://ftp.debian.org/debian experimental mainand apt-cache policy gives me
Package files:
100 /var/lib/dpkg/status
release a=now
990 http://deb.opera.com/opera/ stable/non-free i386 Packages
release o=Opera Software ASA,a=stable,n=stable,l=The Opera web browser,c=non-free
origin deb.opera.com
990 http://deb.opera.com/opera/ stable/non-free amd64 Packages
release o=Opera Software ASA,a=stable,n=stable,l=The Opera web browser,c=non-free
origin deb.opera.com
990 http://dl.google.com/linux/chrome/deb/ stable/main i386 Packages
release v=1.0,o=Google, Inc.,a=stable,n=stable,l=Google,c=main
origin dl.google.com
990 http://dl.google.com/linux/chrome/deb/ stable/main amd64 Packages
release v=1.0,o=Google, Inc.,a=stable,n=stable,l=Google,c=main
origin dl.google.com
500 http://ftp.de.debian.org/debian/ jessie/main Translation-en
500 http://ftp.de.debian.org/debian/ jessie/main i386 Packages
release o=Debian,a=testing,n=jessie,l=Debian,c=main
origin ftp.de.debian.org
500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages
release o=Debian,a=testing,n=jessie,l=Debian,c=main
origin ftp.de.debian.org
500 http://security.debian.org/ wheezy/updates/main Translation-en
990 http://security.debian.org/ wheezy/updates/main i386 Packages
release v=7.0,o=Debian,a=stable,n=wheezy,l=Debian-Security,c=main
origin security.debian.org
990 http://security.debian.org/ wheezy/updates/main amd64 Packages
release v=7.0,o=Debian,a=stable,n=wheezy,l=Debian-Security,c=main
origin security.debian.org
500 http://http.debian.net/debian/ wheezy/non-free Translation-en
500 http://http.debian.net/debian/ wheezy/main Translation-en
500 http://http.debian.net/debian/ wheezy/contrib Translation-en
990 http://http.debian.net/debian/ wheezy/non-free i386 Packages
release v=7.6,o=Debian,a=stable,n=wheezy,l=Debian,c=non-free
origin http.debian.net
990 http://http.debian.net/debian/ wheezy/contrib i386 Packages
release v=7.6,o=Debian,a=stable,n=wheezy,l=Debian,c=contrib
origin http.debian.net
990 http://http.debian.net/debian/ wheezy/main i386 Packages
release v=7.6,o=Debian,a=stable,n=wheezy,l=Debian,c=main
origin http.debian.net
990 http://http.debian.net/debian/ wheezy/non-free amd64 Packages
release v=7.6,o=Debian,a=stable,n=wheezy,l=Debian,c=non-free
origin http.debian.net
990 http://http.debian.net/debian/ wheezy/contrib amd64 Packages
release v=7.6,o=Debian,a=stable,n=wheezy,l=Debian,c=contrib
origin http.debian.net
990 http://http.debian.net/debian/ wheezy/main amd64 Packages
release v=7.6,o=Debian,a=stable,n=wheezy,l=Debian,c=main
origin http.debian.net
1001 http://packages.crunchbang.org/waldorf/ waldorf/main i386 Packages
release o=CrunchBang,a=waldorf,n=waldorf,l=CrunchBang,c=main
origin packages.crunchbang.org
1001 http://packages.crunchbang.org/waldorf/ waldorf/main amd64 Packages
release o=CrunchBang,a=waldorf,n=waldorf,l=CrunchBang,c=main
origin packages.crunchbang.org
Pinned packages:Offline
FFS
deb http://ftp.de.debian.org/debian jessie main
# deb http://ftp.debian.org/debian experimental mainBroken system...
Next!
Offline
FFS
deb http://ftp.de.debian.org/debian jessie main # deb http://ftp.debian.org/debian experimental mainBroken system...
Next!
Sorry, meaning what...?
I think the experimental repo was there from when I installed a newer version of libc6 so I could compile SFML 2.0 libraries. Isnt it commented now though?
Offline
Sorry, meaning what...?
I think the experimental repo was there from when I installed a newer version of libc6 so I could compile SFML 2.0 libraries. Isnt it commented now though?
Your system is broken.
Re-install #!
Offline
BruceJohnJennerLawso wrote:Sorry, meaning what...?
I think the experimental repo was there from when I installed a newer version of libc6 so I could compile SFML 2.0 libraries. Isnt it commented now though?
Your system is broken.
Re-install #!
ahh, okay...?
how can you tell just from that?
Offline
It is not possible to upgrade libc6 in Debian Wheezy.
You might as well run rm -rf /*
Offline
It is not possible to upgrade libc6 in Debian Wheezy.
You might as well run rm -rf /*
so basically its not possible to have SFML 2.0 and a non-broken system?
Oh well theres always next version
Thanks for the help anyways
Offline
It is not possible to upgrade libc6 in Debian Wheezy.
You might as well run rm -rf /*
Looks like the OP's system has been working, although he can't install googleearth now. Is it necessary to re-install before it breaks completely?
@OP You mustn't mix stable and experimental sources, as has been said a million times on these forums. libc6 is a MAJOR component of your system, which many things depend on, so you may be better off just upgrading to unstable anyway.
@Alad has some amusing rants about this topic if you care to search them out 
Artwork at deviantArt; Iceweasel Personas; SLiM #! Themes; Openbox themes
Online
Looks like the OP's system has been working, although he can't install googleearth now. Is it necessary to re-install before it breaks completely?
Well, at least if it's done now the proper backups can be made for a simpler re-install rather than being caught by surprise with a total shutdown.
Offline
damo wrote:Looks like the OP's system has been working, although he can't install googleearth now. Is it necessary to re-install before it breaks completely?
Well, at least if it's done now the proper backups can be made for a simpler re-install rather than being caught by surprise with a total shutdown.
Forgive me for more silly questions, but why would my OS completely melt down? If I dont try to install anything new, it should run perfectly normally, right?
Given that upgrading the libc6 wasnt a great idea, are there any other possible ways to have SFML 2.0 on a stable crunchbang setup? I needed to get the newer version of libc6 in order to properly compile the SFML 2.0 libraries.
Offline
^ It's your system: as the saying goes -- you get to keep the pieces...
Do what you want.
For SFML (whatever that is), maybe try a chroot environment using debootstrap?
Or run a Debian Sid VM inside #!
Or use Arch
Last edited by Head_on_a_Stick (2014-09-12 23:13:04)
Offline
There is a sticky HowTo which may help: LD_LIBRARY_PATH or running new applications in Waldorf
Artwork at deviantArt; Iceweasel Personas; SLiM #! Themes; Openbox themes
Online
^ Didn't think of that...
Good link 
Offline
For SFML (whatever that is), maybe try a chroot environment using debootstrap?
Or run a Debian Sid VM inside #!
Or use Arch
I think I'll pass on arch, but the VM machine sounds like a good idea. The only thing I really needed the libc6 change for was my development stuff under SFML. Running that in a VM until the debian libc6 issue is fixed or SFML 2.0 is finally in the repos sounds fine to me.
The only package that I modified was the libc6, and I commented the testing repository right after, so I think that would be the only package affected on my system. Could I possibly perform the same operation in reverse to reinstall the stable version of libc6 and not have to reinstall #! completely? I did back up my important files like you suggested, but I would like to avoid a complete reinstall if I can.
*EDIT* just saw that link Damo, sounds helpful, Ill take a look at that
Last edited by BruceJohnJennerLawso (2014-09-13 17:44:26)
Offline
^ Yes, you could try...
I use this when I'm stuck:
sudo aptitude -uhttp://www.algebraicthunk.net/~dburrows … 02s04.html
libc6 is used in virtually every package on your system.
If you're properly backed up then you could just carry on using your system & cross your fingers...
Offline
^ Yes, you could try...
I use this when I'm stuck:sudo aptitude -uhttp://www.algebraicthunk.net/~dburrows … 02s04.html
libc6 is used in virtually every package on your system.
Ill take a look at aptitude for it then. Could I not also just select libc6 in Synaptic, select package->force version, and reinstall the 2.13 version that #! came with?
Im just unsure as to why the newer version of libc6 would cause any major breakage though. The hack I applied updated libc6 from 2.13 to 2.19, which I understand to be still within the same header versions (2.xx), but with just some changes to the source code (optimizing functions, fixing bugs, etc.). Why would programs have an issue with a newer version of the library if the functions do more or less the same things? I ask also because I program in C++, and I want to better understand how linux works with libraries and releases.
If you're properly backed up then you could just carry on using your system & cross your fingers...
Yeah, I think I'll just go with that for now. If I desperately need to run something I can just install it on my Kubuntu install, but I like my #! the way it is for the moment, especially for development. If it all falls apart I can just reinstall #! with all the modifications I just backed up.
Offline
Im just unsure as to why the newer version of libc6 would cause any major breakage though. The hack I applied updated libc6 from 2.13 to 2.19, which I understand to be still within the same header versions (2.xx), but with just some changes to the source code (optimizing functions, fixing bugs, etc.). Why would programs have an issue with a newer version of the library if the functions do more or less the same things? I ask also because I program in C++, and I want to better understand how linux works with libraries and releases.
TBH it sounds like you know far more about this sort of thing than me -- I'm just repeating advice I have obtained from reliable sources...
Using synaptic to force a downgrade of libc6 sounds reasonable.
Offline
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.