On Mon, 05 Jul 2004 23:33:47 +1200, Andreas Hagele <andreas fortunecorp co nz> said: > rpm -i glib3-2.4.2-1.i386.rpm > produces: > file /usr/lib/libglib-2.0.so.0 from install of glib2-2.4.2-1 conflicts with > file from package glib2-2.2.1-1 Well, yes. You're trying to -i (install) over an existing version, you probably wanted -F (freshen) or -U instead... > running > rpm -U glib3-2.4.2-1.i386.rpm > produces: > error: Failed dependencies: > glib2 = 2.2.1 is needed by (installed) glib2-devel-2.2.1-1 > > so either way does not work. Why not? -U is "install or freshen, as appropriate". This time, you're trying to upgrade glib2, and getting an error because your existing glib2-devel wants the old version. General rule of thumb: For *any* RPM 'foo', you're just asking for trouble if you manage to get foo and foo-devel on your system with different release numbers. Probably what you wanted for this second one: rpm -U glib2-2.4.2-1.i386.rpm glib2-devel-2.4.2-1.i386.rom (or 'rpm -Uvh' if you like eye candy ;) Note that you may need to get some OTHER rpm's as well - most likely gtk2, gtk2-devel, pango, and pango-devel. (at least on my Fedora Core laptop, although there's other installed RPM's that require glib2, they seem to be agnostic for the glib2-2.2 to glib2-2.4 version).
Attachment:
pgpb4dRKcIi9c.pgp
Description: PGP signature