Tag Info

Hot answers tagged

7

I'm not positive on the settings in Lenny but I know that in Squeeze, sudo is configured with env_reset meaning it will strip out all but a very few select env variables before running the command. This means the DEBIAN_FRONTEND variable you set is never actually making it to the apt-get install --yes --force-yes r-base. If you have full access to sudo, ...


7

ok probably found a solution. first of all go here /lib/x86_64-linux-gnu move these files to /root: libc-2.13.so libdl-2.13.so libm-2.13.so libpthread-2.13.so librt-2.13.so your versions maybe different already. Then lots of things will stop working, you need to launch bash with predefined LD_PRELOAD: ...


3

First, you do what it told you to do. A copy of the C library was found in an unexpected directory: '/lib/x86_64-linux-gnu/libc-2.13.so' It is not safe to upgrade the C library in this situation; please remove that copy of the C library or get it out of '/lib/x86_64-linux-gnu' and try again. Maybe that will fix everything. But you still have enough ...


2

It is possible to recover from a mistake like that without shutting the system down, but it tends to involve deep Unix voodoo. You would need to figure out which commands do still work (these will be the ones that were statically linked when they were compiled) and from those, figure out a way to get another identical copy of libc6 back on the system, in ...


2

don't use testing packages in lenny (oldstable!). Your system will be screwed if you force this. What`s the reason why you do this? Which software do you want to upgrade (and to which version?)


2

A more concise variant of the debconf solution mentioned in another answer is the following: echo 'libc6 libraries/restart-without-asking boolean true' | sudo debconf-set-selections I just used this solution successfully when upgrading glibc on Debian 7 (wheezy). For the curious, the way I found the right configuration variable to set was as follows: ...


2

Besides what we discussed in email, there is also the saying If you can't beat'em, join'em. so you could create a virtual machine on your laptop which corresponds to the (base) packages on the cloud instance, and then rebuild your own local R 2.12.1 .deb against those packages. As no upgraded libc6 is involved, you'd sidestep the issue. Or, in ...


2

Not sure if this would have helped with part of it, but if you ever find you've moved the runtime linker so that things like mv,cp,ln,rm no longer work, you can still run them (and hopefully rescue yourself) by specifying the runtime linker explicitly. E.g. mv /lib64 /tmp ln -s /lib /lib64 # fails, no runtime linker /tmp/lib64/ld-2.13.so ...


2

Looks like you overwrote one of the links for your C library. Why did you do this? There's no reason you should be modifying links or library files. Where did /lib/libc.so.1 come from? Cecking my CentOS 4, 5 and 6 systems, that file is not included in the distribution. What version of CentOS is this? On CentOS 5, libc.so.6 should link to libc-2.5.so. ...


1

You may be able to recover from your error by running ldconfig.


1

First, you do what it told you to do: You might want to run 'apt-get -f install' to correct these. If this doesn't correct the problem, then do all of the following: Check /etc/apt/sources.list and make sure you are on a single version (e.g. squeeze) and haven't tried to mix in sources from unstable/testing, etc. Run apt-get clean. Run apt-get update. ...


1

Step 1 On the host that had the package installed manually (interactive option selection) run: apt-get install debconf-utils debconf-get-selections > answers.conf Step 2 (Optional) At this point you may want to filter answers.conf to include the configuration answers only for specific package(s). I tested without filtering. Step 3 When creating ...


1

I was able to deduce that the libc6 installer was prompting to restart cron even if cron was not running which seems odd. At any rate I was able to get around that by renaming the cron init.d scripts so that the package installer was fooled into not thinking cron was present. Ugh. What a mess: sudo /etc/init.d/mysql stop sudo /etc/init.d/exim4 stop sudo ...


1

This looks like a frankenstein of a system that a vendor put together: Debian hasn't shipped with a 2.6.18 kernel since Etch (4.0), but the kernel timestamp is after Etch's EOL. Additionally that kernel number system isn't Debian, so it is clearly a custom kernel. libc6 version could be that from Squeeze (6.0), but gcc clearly is not. In fact, that gcc ...


1

You've now partially upgraded your system to testing, skipping a stable release (squeeze). This is strongly discouraged. Here are your options as I would recommend them: Upgrade to squeeze (the current 'stable'), then upgrade to wheezy (the current 'testing'). You will be running testing at least until wheezy is released as stable. This is not a good ...


1

I'm not very familiar with Ubuntu, but you should be able to boot from the installation media as rescue, and from there reinstall the glibc package. Go check their website (or Debian's) for more detailed instructions.



Only top voted, non community-wiki answers of a minimum length are eligible