The following ERRATA for SL 30rolling i386 are now available from:
ftp://ftp.scientificlinux.org/linux/scientific/30rolling/i386/errata/SL/RPMS/

	gtk2-2.2.4-15.SL.1.i386.rpm
	gtk2-devel-2.2.4-15.SL.1.i386.rpm
	librsvg2-2.2.3-6.SL.4.i386.rpm
	librsvg2-devel-2.2.3-6.SL.4.i386.rpm

Because of the strangeness that has ensued with the interaction of the 
newer gtk2 and librsvg2, the following errata had the following fixes 
put in place.

gtk2
   checks to see what arch you have, and if necessary, whether you have 
the 64 bit or 32 bit version of gtk2 installed.  It then makes a link to 
/usr/bin/gdk-pixpuf-query-loaders from 
/usr/bin/gdk-pixpuf-query-loaders(-32) or (-64), depending on the 
situation, if a link is not already there.

librsvg2
   checks to see what arch you have, and if necessary, whether you have 
the 64 bit or 32 bit version of gtk2 installed.  It then makes a link to 
/usr/bin/gdk-pixpuf-query-loaders from 
/usr/bin/gdk-pixpuf-query-loaders(-32) or (-64), depending on the 
situation, if a link is not already there.
   (We realize this might be a little overkill.  These two rpm's tend to 
not be updated alot.  So we figured we'd put this fix in both of them, 
so that if one of them was updated, the other would still pass on this fix.)
   It now checks to see if /usr/bin/update-gdk-pixbuf-loaders is there 
before running it's scripts, just incase it get's updated before the 
gtk2 does.

For both rpm's we have modified the .rpmmacros so that they have the 
proper arch.  By doing this both gtk2 and librsvg2 will be pointing 
their stuff at the proper i386-redhat-linux-gnu, instead of each 
pointing to something different.  (They are using two totally different 
variables to point at the same directory, which caused some problems.)
Since we made this change in the .rpmmacros build file for the errata 
area, this change will be continued with further errata.

If people could test these rpm's we would appreciate it.  I have put 
them through many tests of updates and installs and they all seems to 
work ok.
If no problems are found, we will put them in the errata area next week.

Troy Dawson