On Sat, Jul 7, 2012 at 5:57 PM, Uli Armbruster <uli.armbruster@xxxxxxxxxxxxxx> wrote: > Is this caused by the fact that there are two packages with files in /lib ? How can I solve this problem? Is it ok this time to force the update? > > I _could_ remove lib32-glibc first, run the update and then reinstall my lib32 stuff, since I don't have much lib32 stuff installed. But I think for many people this isn't an option! That's why I'm asking here. I hit the same problem myself, and used `pacman -Rdd` to temporarily remove lib32-glibc bypassing the dependency checks. After upgrade, `pacman -S --asdeps lib32-glibc` to reinstall. -- Mantas Mikulėnas
