apt-get install build-essential fails

[rbirkner]

I am trying to install BIRD on the vm. Therefore, I have to install build-essential (gcc, make...). However , I tried both ways of installing packages as described in the FAQ section and always the same error happens:
The following packages have unmet dependencies:
build-essential: Depends: libc6-dev but itis not going to be installed or libc-dev
....
locales: Depends: glibc-2.19-1
E: Unmet dependecies. Try 'apt-get -f install'

So, I tried 'apt-get -f install' but it also fails with some error.
Any ideas?

I also tried following the solution for the following issue (#26). Unfortunately, it did not help either.

[maxonthegit]

Hi,

the dependency problem you are experiencing is likely due to the fact that, unfortunately, the Netkit filesystem image is now somewhat out of sync with respect to the current contents of the Debian unstable repository. However, you can easily solve your problem by proceeding as follows.

First of all, start an Internet-connected virtual machine and edit file /etc/apt/sources.list by removing the line pointing to the ftp.it.debian.org repository and replacing it with the following:

deb http://archive.debian.org/debian/ lenny main contrib non-free

Set up a DNS server inside /etc/resolv.conf, then refresh the package index by launching an "apt-get update". At this point you should be able to install bird flawlessly (I have just made a quick check and the installation succeeds).

Hope this helps.

On 02/23/2015 12:03 PM, rbirkner wrote:

I am trying to install BIRD on the vm. Therefore, I have to install build-essential (gcc, make...). However , I tried both ways of installing packages as described in the FAQ section and always the same error happens:
The following packages have unmet dependencies:
build-essential: Depends: libc6-dev but itis not going to be installed or libc-dev
....
locales: Depends: glibc-2.19-1
E: Unmet dependecies. Try 'apt-get -f install'

So, I tried apt-get -f install but it also fails with some error.
Any ideas?

—
Reply to this email directly or view it on GitHub #34.