On 01/08/2012 06:12 PM, Sander Jansen wrote:
:: Synchronizing package databases...
testing 29.7 KiB 238K/s 00:00 [######################] 100%
core 102.1 KiB 296K/s 00:00 [######################] 100%
extra 1170.6 KiB 816K/s 00:01 [######################] 100%
community-testing 11.1 KiB 244K/s 00:00 [######################] 100%
community 999.7 KiB 673K/s 00:01 [######################] 100%
multilib-testing 1574.0 B 71.5M/s 00:00 [######################] 100%
multilib 67.8 KiB 339K/s 00:00 [######################] 100%
:: 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...
error: failed to prepare transaction (could not satisfy dependencies)
:: gcc: requires gcc-libs=4.6.2-1
:: valgrind: requires glibc<2.15
Any suggestions on how to fix this conflict?
Thanks,
Sander
I occasionally get dependency errors when there is a pacman upgrade. I've gotten
around it every single time by explicitly update pacman (pacman -S pacman),
followed by my normal upgrade (pacman -Su)
