Hi, Guillem Jover <guil...@debian.org> wrote: And to the gconf maintainers, does its trigger really need to be synchronous (i.e. do trigggering packages need to await the trigger processing)? Or in other words do those other triggering packages require the trigger to be processed to be able to consider themselves configured and able to satisfy dependencies?
The package (typically an end-user application) is not usable until the trigger has been run. That said, the dependencies of a package using GConf would not usually require the trigger to have run for their own postinst to run successfully. I cannot exclude a corner case where a dependency would use a binary needing registered GConf schemas in its postinst, but it is definitely not the typical use case. So it could probably be migrated to a noawait trigger. The same holds for the /usr/share/glib-2.0/schemas trigger in libglib2.0-0 (but probably not the other triggers of the same package). Cheers, -- Joss -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org