Bug#578057: I am confused...now everything works fine

[Alexander Kurtz]

Hi,

First a small correction on my earlier mail: gconf-schemas is actually
not run by the postinst script, see line 28-31
of /usr/sbin/gconf-schemas. Instead the package gconf2 sets up a trigger
monitoring files under /usr/share/gconf/{defaults,mandatory,schemas}. 

gconf2's postinst contains this:

  if [ "$1" = triggered ]; then
     for trigger in $2; do
         case $trigger in
             /usr/share/gconf/schemas)
                 gconf-schemas --register-all --no-signal
                 ;;
             /usr/share/gconf/defaults)
                 update-gconf-defaults --no-signal
                 ;;
             /usr/share/gconf/mandatory)
                 update-gconf-defaults --no-signal --mandatory
                 ;;
         esac
     done
     signal_daemons
     exit 0
  fi

So it's always --register-all and never just --register.

Secondly, the test procedure I described three hours ago, does now work
as expected on all machines (i386 and amd64). The gconf database is
always updated correctly when downgrading/upgrading.

I am really confused now. Upgrading this afternoon produced a corrupt
gconf database on two machines. Now everything works fine. I probably
had some bad karma this afternoon.

I hope that I could at least help some people.

Alexander Kurtz 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20100425/2d3b8d58/attachment.pgp>