/lib/powerpc-linux-gnu is not unexpected

[James Troup]

| Setting up libc-bin (2.15-0ubuntu10) ...
| (Reading database ... 13721 files and directories currently installed.)
| Preparing to replace libc6 2.15-0ubuntu6 (using .../libc6_2.15-0ubuntu10_powerpc.deb) ...
|
| A copy of the C library was found in an unexpected directory:
| '/lib/powerpc-linux-gnu/libc-2.15.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/powerpc-linux-gnu' and try again.
|
| dpkg: error processing /var/cache/apt/archives/libc6_2.15-0ubuntu10_powerpc.deb (--unpack):
| subprocess new pre-installation script returned error exit status 1
| No apport report written because MaxReports is reached already
| Errors were encountered while processing:
| /var/cache/apt/archives/libc6_2.15-0ubuntu10_powerpc.deb
| E: Sub-process /usr/bin/dpkg returned an error code (1)
| root@royal:/#

Physician, heal thyself!

| root@royal:/# dpkg -c /var/cache/apt/archives/libc6_2.15-0ubuntu10_powerpc.deb | grep /lib/powerpc-linux-gnu/ -c
| 300

[Adam Conrad (adconrad)]

I'd love a copy of the chroot you're blowing up, if you can find a chance to tar it up and drop it somewhere for me. This code isn't arch-specific, and exists on both Debian and Ubuntu, so you being the first/only person to make it explode is vaguely fascinating to me.

While it may be "something you've done", it's just as likely that it's just a bizarre corner case that should be made more robust. I've heard it's kinda cool to have a C library when you're done upgrading.