karniv0re's Journal: libc.so.6

For future reference, removing the libc.so.6 soft link is a bad idea in any case. You will have to boot a live cd just to reapply the soft link (I booted Slax, because Knoppix is a piece of shit sometimes).

But seriously. If you remove that link, you will lose access to pretty much anything that was written in C/C++. Like cp. And mv. And fucking ln. Yeah. So you'll be fucked. Don't do it.

Right now I've got some issues with apt being broken. I get this crap:

$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree... Done
Correcting dependencies... Done
The following extra packages will be installed:
libc6
Suggested packages:
glibc-doc
The following packages will be upgraded:
libc6
1 upgraded, 0 newly installed, 0 to remove and 166 not upgraded.
2 not fully installed or removed.
Need to get 0B/4183kB of archives.
After unpacking 207kB of additional disk space will be used.
Do you want to continue [Y/n]? Y
(Reading database ... 124006 files and directories currently installed.)
Preparing to replace libc6 2.3.6.ds1-13etch2 (using .../libc6_2.3.6.ds1-13etch5_amd64.deb) ...
Unpacking replacement libc6 ...
dpkg: error processing /var/cache/apt/archives/libc6_2.3.6.ds1-13etch5_amd64.deb (--unpack):
trying to overwrite `/usr/lib64', which is also in package nspluginwrapper
Errors were encountered while processing:
/var/cache/apt/archives/libc6_2.3.6.ds1-13etch5_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Currently investigating a fix.

nspluginwrapper

[Qzukk]

Wherever you got that nspluginwrapper package (I don't see it in Debian), complain to that person, they packaged it wrong, directories not specific to that package should not appear in that package's contents.

The fast way to get this working is to go into /var/cache/apt/archives/ where it downloads the .deb files, and run dpkg --install --force-overwrite libc6etcetcetc WARNING if you uninstall the nspluginwrapper package after this it May or May Not remove your /usr/lib64 directory with all of the tasty im

Oh wait, I see what they did there...

[Qzukk]

I'm guessing that Kubuntu either has a symlink from /usr/lib -> /usr/lib64 or from /usr/lib64 -> /usr/lib (debian has this), and whoever made that package had the opposite, so in one package, it's a symlink, and the other is a directory.

Without seeing both package contents, it's hard to say what will happen if you force one or the other.

On second thought, don't listen to strangers

[Qzukk]

I thought of a third option, that the libc6 you're installing does the symlink the opposite way from the libc6 you have installed now, in which case --force-overwrite would probably make the system blow up worse than that time you deleted the symlink...

The 166 held packages makes me think you're not getting this libc6 from the same place you've been getting your packages before... maybe you need a dist-upgrade to change distribution versions?