[Bug 1041742] New: Filetriggers do not fire (reliably)
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742 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 http://download.opensuse.org/repositories/GNOME:/Medias/images/iso/?P=GNOME_... 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 completely) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c1
Michael Andres
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)
If a package contains a %posttrans script, zypp passes '--noposttrans' to the rpm install command. Maybe this disturbs? I don't know what else in libzypp could influence this, as we don't use librpm, but exec 'rpm' to install the package. The exact rpm command is visible in the zypper.log (grep "Executing 'rpm'" /var/log/zypper.log). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c2
--- Comment #2 from Dominique Leuenberger
(In reply to Dominique Leuenberger from comment #0)
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)
If a package contains a %posttrans script, zypp passes '--noposttrans' to the rpm install command. Maybe this disturbs? I don't know what else in libzypp could influence this, as we don't use librpm, but exec 'rpm' to install the package.
The exact rpm command is visible in the zypper.log (grep "Executing 'rpm'" /var/log/zypper.log).
ok, so gdm having a posttrans might indeed be the reason that rpm also skips the transfiletriggerin - which is, after all, also a post-trans script I'll do some tests on my VM to confirm that this is indeed the case when using rpm.. and if so, we need to find a solution -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c3
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c4
Michael Andres
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Antoine Belvire
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Luciano Santos
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c13
Ludwig Nussel
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c14
--- Comment #14 from Dr. Werner Fink
@mls: Leaving it up to you. A bug to fix or WONTFIX?
Can we please solve this with as *working* solution ... compare with boo#1152105 and SR#713226 Those %filetranstriggerin / %transfiletriggerun are perfect to reduce time on enabling info nad manual pages without using cron or time consuming single calls -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c15
--- Comment #15 from Dr. Werner Fink
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c16
Dr. Werner Fink
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Dr. Werner Fink
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c17
--- Comment #17 from Dr. Werner Fink
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Dan Čermák
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Neal Gompa
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c19
--- Comment #19 from Michael Andres
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c20
Michael Andres
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Ludwig Nussel
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c24
Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Frederic Crozat
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Michael Andres
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Neal Gompa
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c27
--- Comment #27 from OBSbugzilla Bot
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Bj�rn Voigt
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c28
--- Comment #28 from Luciano Santos
$ rpm -q rpm rpm-4.17.1.1-2.1.x86_64
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c29
Michael Andres
I've tested here on my Tumbleweed system, using a dummy package to echo
Please try also with the new installer backend. It should behave much better than the old one. Especially regarding thrigers. Enable it by calling `ZYPP_SINGLE_RPMTRANS=1 zypper ...` Or persistently enable it in /etc/zypp/zypp.conf's [main] section by setting [main] techpreview.ZYPP_SINGLE_RPMTRANS=1 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c30
--- Comment #30 from Luciano Santos
(In reply to Luciano Santos from comment #28)
I've tested here on my Tumbleweed system, using a dummy package to echo
Please try also with the new installer backend. It should behave much better than the old one. Especially regarding thrigers. Enable it by calling `ZYPP_SINGLE_RPMTRANS=1 zypper ...` Or persistently enable it in /etc/zypp/zypp.conf's [main] section by setting [main] techpreview.ZYPP_SINGLE_RPMTRANS=1
Alright, with this new installer backend, things got much better. In a DUP with 114 updates, tranfiletrigger(in|postun) is invoked only once (and I think that in my previous test I messed up the transfiletriggerpostun scriptlet, thus it didn't run). And I saw that, apparently, Zypper is converting filetriggers to triggers. I'm going to keep an eye on the next DUPs. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c31
--- Comment #31 from Michael Andres
And I saw that, apparently, Zypper is converting filetriggers to triggers. I'm going to keep an eye on the next DUPs.
The new backend is purely driven by librpm, so such a conversion would be done by rpm. But it could also be a matter of our reporting. If you find an issues, please try to provide a small screenshot or description and please attach the /var/log/zypper.log so we can investigate. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply@novell.com
-
bugzilla_noreply@suse.com