Bug ID 1041742
Summary Filetriggers do not fire (reliably)
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component libzypp
Assignee zypp-maintainers@forge.provo.novell.com
Reporter dimstar@opensuse.org
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

In GNOME:Next, we started experimenting with file triggers (with the goal to
lower the number of bugs based on missing post scripts)

As a sample, I implemented this trigger (on glib2-tools):

%transfiletriggerin -n glib2-tools -- %{_datadir}/glib-2.0/schemas
%{_bindir}/glib-compile-schemas %{_datadir}/glib-2.0/schemas

%transfiletriggerpostun -n glib2-tools -- %{_datadir}/glib-2.0/schemas
%{_bindir}/glib-compile-schemas %{_datadir}/glib-2.0/schemas

The trigger is confirmed to work, but in some cases, it seems not to fire, eg
on the package 'gdm'

(which is currently the reason why
fails to boot to desktop)

zypper in --no-recommends gdm => the file trigger is not executed
rpm -i gdm-3.24.1.rpm         => the trigger actually seems to work (which is
why I file it against libzypp)

This currently stops us from moving forward and proposing file triggers to be
more widely used (even though I think they can solve quite some packaging bugs)

The packages in question for testing are all in the GNOME:Next repository
(glib2 which has the trigger, it has the %glib2_gsettings_schema_post set to
%nil, so packages that use it in their post script only get a dummy - once the
implementation is complete, we will of course go and clean those out

You are receiving this mail because: