:: 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

>
> 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.

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)

On Mon, Jan 9, 2012 at 4:28 AM, Matthew Monaco <dgbaley27@0x01b.net> wrote:
> 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)

Do you have 'SyncFirst = pacman' in your pacman.conf?

On Jan 8, 2012 8:35 PM, "Qadri" <Muhammad.A.Qadri@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.

Sander

On 9 January 2012 12:24, Sander Jansen <s.jansen@gmail.com> wrote:
> On Jan 8, 2012 8:35 PM, "Qadri" <Muhammad.A.Qadri@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...

On 01/08/2012 08:55 PM, Karol Blazewicz wrote:

On Mon, Jan 9, 2012 at 4:28 AM, Matthew Monaco<dgbaley27@0x01b.net> wrote:

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)


Do you have 'SyncFirst = pacman' in your pacman.conf?


yes

On Sunday 08 Jan 2012 19:12:57 Sander Jansen 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?

Probably either wait a bit or else try a different mirror. Sounds like the
mirror got out of sync.

HTH,

Pete.

On Mon, Jan 9, 2012 at 2:53 AM, Peter Lewis <plewis@aur.archlinux.org> wrote:
> On Sunday 08 Jan 2012 19:12:57 Sander Jansen 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?
>
> Probably either wait a bit or else try a different mirror. Sounds like the
> mirror got out of sync.
>

Or perhaps my lack of updating in recent weeks made things out of
whack. Just updating all packages including pacman at the same time
seems to do the trick.

Sander