From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/20110330/003801.html | 90 +++++++++++++++++++++++++++++++++ 1 file changed, 90 insertions(+) create mode 100644 zarb-ml/mageia-dev/20110330/003801.html (limited to 'zarb-ml/mageia-dev/20110330/003801.html') diff --git a/zarb-ml/mageia-dev/20110330/003801.html b/zarb-ml/mageia-dev/20110330/003801.html new file mode 100644 index 000000000..29d7130b5 --- /dev/null +++ b/zarb-ml/mageia-dev/20110330/003801.html @@ -0,0 +1,90 @@ + + + + [Mageia-dev] cairo and poppler conflicts + + + + + + + + + +

[Mageia-dev] cairo and poppler conflicts

+ Olivier Blin + mageia at blino.org +
+ Wed Mar 30 17:45:34 CEST 2011 +

+
+ +
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.
+
+-- 
+Olivier Blin - blino
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1