On Tue, 28 Jun 2011 09:31:44 -0400, John A. Sullivan III wrote: > On Tue, 2011-06-28 at 13:16 +0000, Camaleón wrote:
>> > What happened and how do I fix it? This is a bit of a disaster. >> > Thanks >> >> Google seems to point at GTK+ 2/3 conflicts. >> >> Is it possible that some GTK+ libraries have been updated to newer >> versions because of the above wheezy pinning? :-? >> >> >> > That's what I'm guessing but I don't see it: > > ii libgtk2.0-0 2.24.4-3 The GTK+ graphical user interface > library > ii libgtk2.0-bin 2.24.4-3 The programs for the GTK+ graphical > user interface library > ii libgtk2.0-common 2.20.1-2 Common files for the GTK+ graphical > user interface library I would put the focus into the "upgraded" packages: libgail18:i386 (2.20.1-2, 2.24.4-3) libwmf0.2-7:i386 (0.2.8.4-6.1+b1, 0.2.8.4-8) libgtk2.0-bin:i386 (2.20.1-2, 2.24.4-3) libgeoip1:i386 (1.4.7~beta12+dfsg-1, 1.4.7+dfsg-2) wireshark:i386 (1.2.11-6+squeeze1, 1.6.0-1) librsvg2-2:i386 (2.26.3-1, 2.34.0-1) librsvg2-common:i386 (2.26.3-1, 2.34.0-1) libgtk2.0-0:i386 (2.20.1-2,2.24.4-3) wireshark-common:i386 (1.2.11-6+squeeze1, 1.6.0-1) > Everything is 2.x although I wonder why common is a different version. Updated versions are from wheezy, as you say below. > I'll try updating that next. I also don't know why libraries would have > been brought in from Wheezy since it is pinned lower than Squeeze. > Wireshark should have been in Squeeze so it should not have pulled it > from Wheezy and the same for any libraries. Thanks - John I can't help for the pinning issue, that thingy looks like a sort of "black magic" to me :-). But yes, it seems they're now from wheezy and that pulled the updated GKT+ libraries so I would try to return back the packages to the old version and see how it goes. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.06.28.14.35...@gmail.com
