Supposedly this bug is fixed in the new pacman upgrade, the correct solution would be to just say no to upgrading pacman first. this will solve your problem now. The reason it wasn't working earlier was becasue gcc was released with version 4.7.0-4 and gcc-multilib was still providing version 4.7.0-3 so every thing was conflicting. Since gcc-multilib 4.7.0-4 was just released to the multilib repository, If you still have an error where saying to to syncing pacman first doesn't solve it, get a mirror that has synced more recently and they do pacman -Syyu and still say no to pacman first.
On Wed, Apr 11, 2012 at 06:54:54PM +0200, Christoph Vigano wrote: > On 04/11/2012 06:49 PM, Madhurya Kakati wrote: > > Hi, > > I am unable to update my system. I guess this problem has occurred to me > > before > > but unfortunately I forgot how to get around it. > > > > [papul@archlinux ~]$ sudo pacman -Su > > Password: > > :: The following packages should be upgraded first : > > pacman > > :: Do you want to cancel the current operation > > :: and upgrade these packages now? [Y/n] y > > > > resolving dependencies... > > looking for inter-conflicts... > > :: gcc-libs and gcc-libs-multilib are in conflict. Remove > > gcc-libs-multilib? [y/N] y > > error: failed to prepare transaction (could not satisfy dependencies) > > :: gcc-multilib: requires gcc-libs-multilib=4.7.0-3 > > > > I resolved this with pacman -S pacman first and -Syu after that. > Worked flawlessly (that was the solution the last time). > > Christoph >
pgp9QFc4gxuMh.pgp
Description: PGP signature
