Frank Griffin <[email protected]> writes: > On 03/29/2011 03:01 PM, Ahmad Samir wrote: >> [...] >> “attach”... >> >> Anyway, from the log: >> auto-select: adding lib64cairo-xcb2-1.10.2-4.mga1.x86_64 replacing >> lib64cairo-xcb2-1.10.2-3.mga1.x86_64 >> >> which means you have lib64cairo-xcb2 installed (rpm -qa lib64cairo* >> should confirm/deny); this is not the default, urpmi is set to prefer >> lib(64)cairo2 over lib(64)cairo-xcb2, so I think, 'urpmi lib64cairo2' >> should fix this issue. > > You're correct, but I'm damned if I know why. I have two cauldron > systems which get updated via --auto-update exclusively. On one, I > have >
[...] > Thanks for the assist, and sorry for the noise. There might have been a bug for a short time where pkgconfig(cairo) got resolved to cairo-xcb-devel, so it is possible the wrong package got pulled at some point. It should not be the case anymore (with a fix in urpmi prefer.vendor.list), but it won't be fixed automatically for cauldron users that got the "wrong" package before. -- Olivier Blin - blino
