Well I have no Idea why it has additional copys of libc.
After the bug was active a second time, and the posted solution does not
worked, I installed a other distribution because I have to work with the
system.
Missing security updates are than no goog idea.
Generally I'm missing a build in-solv
This is not a bug. It's quite intentional that libs's preinst bombs if
you have extra copies of libc (in this case, an ancient libc 2.11?) in
your search path. Is there a reason you need that there?
** Changed in: eglibc (Ubuntu)
Status: New => Invalid
--
You received this bug notificat
Workaround with uncommenting the exit 1 in preinst of libc.
Followring the :
http://yeupou.wordpress.com/2012/07/21/modifying-preinst-and-postinst-scripts-before-installing-a-package-with-dpkg/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
