Ok, thanks for following up on this. If you are on a 32-bit, then you
shouldn't have this symbolic link from /usr/lib64 to /usr/lib -- this is
only correct for 64-bit systems. If I manually add this link on a 32-Bit
system I can reproduce the error, so that really seems to be the cause
of the problem! I'm not sure whether an old version of fakeroot or
another package is responsible for this wrong link.
I think the following should work (DISCLAIMER: The first step might break your
system by removing your graphics driver, so maybe not do this on a system where
the failing update of fakeroot is just a minor annoyance...):
1. remove the old fakeroot package:
sudo apt-get remove fakeroot
Note that this will also remove packages depending on fakeroot, e.g. nvidia
or flgrx drivers -- take a note which packages were removed
2. Check whether the symlink still exists, i.e.
ls -ld /usr/lib64
If you get "No such file or directory", continue with step 5
3. *If* there is still a symlink, make sure no package claims it:
dpkg -S /usr/lib64
This should issue "/usr/lib64 not found"
4. Manually remove the symlink:
sudo rm /usr/lib64
5. Reinstall fakeroot and/or packages depending on fakeroot (that were removed
in step 1)
** Changed in: fakeroot (Ubuntu)
Status: Incomplete => Confirmed
--
package fakeroot (not installed) failed to install/upgrade: unable to open
'/usr/lib64/libfakeroot/libfakeroot-tcp.so.dpkg-new': No such file or directory
https://bugs.launchpad.net/bugs/565724
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
