[Mageia-dev] cairo and poppler conflicts
shikamaru at mandriva.org
Sat Apr 2 09:57:19 CEST 2011
On Wed, Mar 30, 2011 at 05:45:34PM +0200, Olivier Blin wrote:
> Frank Griffin <ftg at roadrunner.com> 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.
Yep, sorry for that, I was unaware of that pkgconfig(cairo) provides.
But f-spot’s case has been bugging me for quite some time.
I don’t use it so I could not see the issue, but I don’t understand why
it does have an explicit require on lib64cairo2…
all its dependencies don’t.
Here are the requires of f-spot :
As you can see, lib64cairo2 is completely unnecessary because the
package already requires libcairo.so.2()(64bit).
Looking at the spec:
I don’t understand line 43 to 45 though I’m not sure these are the one
that pulls cairo, nor do I understand which problem Götz tried to work
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
More information about the Mageia-dev