On Sun, 10 Mar 2013 09:57:38 -0600, Kevin Fenzi wrote:
Odd. Sounds as if it's too late to examine the problem, which isn't
documented in that thread. The Python source code performs a GConf
settings check and tries to install the schemas file on error condition.
Funny stuff, but shouldn't be difficult to debug.
It seems I'm not up-to-date with regard to the %pre and %post scriptlets
for GConf:
https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#GConf
Why does %post uninstall the new .schemas file? Shouldn't it use the
old copy from the previous package release that was saved in %pre in
/var/lib/rpm-state/gconf?
$ rpm --eval %gconf_schema_upgrade
for schema in ; do
if test -f /var/lib/rpm-state/gconf/"$schema".schemas ; then
cmp --quiet /etc/gconf/schemas/"$schema".schemas
/var/lib/rpm-state/gconf/"$schema".schemas
if test $? != 0; then
if test -f /etc/gconf/schemas/"$schema".schemas ; then
export GCONF_CONFIG_SOURCE=`gconftool-2 --get-default-source`
gconftool-2 --makefile-uninstall-rule
/etc/gconf/schemas/"$schema".schemas > /dev/null || :
#
# (!) Why does it uninstall the new schemas file?
#
fi
export GCONF_CONFIG_SOURCE=`gconftool-2 --get-default-source`
gconftool-2 --makefile-install-rule
/etc/gconf/schemas/"$schema".schemas > /dev/null || :
fi
rm -f /var/lib/rpm-state/gconf/"$schema".schemas
else
export GCONF_CONFIG_SOURCE=`gconftool-2 --get-default-source`
gconftool-2 --makefile-install-rule /etc/gconf/schemas/"$schema".schemas
> /dev/null || :
fi
done