[arch-general] pacman update conflict

[Gergely Imreh]

On 9 January 2012 12:24, Sander Jansen <s.jansen at gmail.com> wrote:
> On Jan 8, 2012 8:35 PM, "Qadri" <Muhammad.A.Qadri at gmail.com> wrote:
>>
>> >
>> > 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
>> >
>>
>> If you're okay with updating those two packages after you update pacman,
>> (and you're not planning on running gcc or valgrind in between), then
>> ignore the dependency check. Alternatively, don't update pacman first -
>> though not knowing what version of pacman you're using, it's hard to say
>> whether or not it'll be critical.
>>
>> MAQ.
>
> Current pacman is 4.0.1-1.

Is it really? I think the 4.0.1 is only in testing, normal updates are
at 3.5.4-4...