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)
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742 http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c1
Michael Andres ma@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dimstar@opensuse.org Flags| |needinfo?(dimstar@opensuse. | |org)
--- Comment #1 from Michael Andres ma@suse.com --- (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).
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742 http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c2
--- Comment #2 from Dominique Leuenberger dimstar@opensuse.org --- (In reply to Michael Andres from comment #1)
(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
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742 http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c3
Dominique Leuenberger dimstar@opensuse.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dimstar@opensuse. | |org) |
--- Comment #3 from Dominique Leuenberger dimstar@opensuse.org --- Confirmed: rpm --noposttrans actually also skips the transaction file triggers
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742 http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c4
Michael Andres ma@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mls@suse.com Flags| |needinfo?(mls@suse.com)
--- Comment #4 from Michael Andres ma@suse.com --- @mls: is there a way to circumvent this?
But even if, we still face the fact that every package forms it's own transaction. So %transfiletrigger will behave more or less the same as a %filetrigger.
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Antoine Belvire antoine.belvire@opensuse.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |antoine.belvire@opensuse.or | |g
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Luciano Santos luc14n0@linuxmail.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |luc14n0@linuxmail.org
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Dominique Leuenberger dimstar@opensuse.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Filetriggers do not fire |transfiletriggerin and |(reliably) |transfiletriggerpostun are | |not executed by libzypp
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742 http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c13
Ludwig Nussel lnussel@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P1 - Urgent
--- Comment #13 from Ludwig Nussel lnussel@suse.com --- This needs an answer and a fix or documentation to avoid wasting time on something that is know to fail.
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 werner@suse.com --- (In reply to Michael Andres from comment #12)
@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
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 werner@suse.com --- As well as SR#733634
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742 http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c16
Dr. Werner Fink werner@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ma@suse.com Assignee|mls@suse.com |ma@suse.com
--- Comment #16 from Dr. Werner Fink werner@suse.com --- Correct maintainer for libzypp to get a working solution
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Dr. Werner Fink werner@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1133764
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 werner@suse.com --- The tracker bug boo#1133764 ... with subject:
[TRACKER] port packages to use file triggers
can not be done without working libzypp
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Dan Čermák dcermak@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dcermak@suse.com
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Neal Gompa ngompa13@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ngompa13@gmail.com
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742 http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c19
--- Comment #19 from Michael Andres ma@suse.com --- - Without fixing rpm, %transfiletrigger* will not be executed because --noposttrans also disables the %transfiletrigger in rpm.
- Even if rpm would be fixed and would execute %transfiletrigger, they will behave the same way as if you use ordinary %filetrigger* due to the way we use rpm.
Workaround could be to use %filetrigger to touch some indicator file and a posttrans rebuilding the cache if the indicator file exists. This should work no matter if rpm gets fixed or not.
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742 http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c20
Michael Andres ma@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mls@suse.com)
--- Comment #20 from Michael Andres ma@suse.com --- (No matter whom it is assigned to) @mls: Can we have an option to let rpm execute the %transfiletrigger even if --noposttrans is passed?
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Ludwig Nussel lnussel@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel@suse.com
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742 http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c24
Franck Bui fbui@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fbui@suse.com
--- Comment #24 from Franck Bui fbui@suse.com --- FWIW systemd needs this feature too so many heavy actions would be executed only once during system updates, see [1] for details.
[1] https://github.com/systemd/systemd/blob/master/src/core/triggers.systemd.in
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Frederic Crozat fcrozat@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fcrozat@suse.com
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Michael Andres ma@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |libzypp Assignee|ma@suse.com |zypp-maintainers@suse.de
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Neal Gompa ngompa13@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Blocks|1180721 |
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742 http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c27
--- Comment #27 from OBSbugzilla Bot bwiedemann+obsbugzillabot@suse.com --- This is an autogenerated message for OBS integration: This bug (1041742) was mentioned in https://build.opensuse.org/request/show/910984 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/910985 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/910986 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/910987 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/910988 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/910989 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/910990 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/910991 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/910992 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/910993 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/910994 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/910995 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/910996 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/910997 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/910998 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/910999 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/911000 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/911001 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/911002 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/911003 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/911004 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/911005 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/911006 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt https://build.opensuse.org/request/show/911007 Backports:SLE-15-SP3 / rubygem-bcrypt_pbkdf-1.1+rubygem-childprocess-4.1+rubygem-erubi-1.10+rubygem-i18n-1.8+rubygem-listen-3.6+rubygem-mime-types-3.3+rubygem-net-scp-3.0+rubygem-net-sftp-3.0+rubygem-net-ssh-6.1+rubygem-rake-13.0+rubygem-rb-fsevent-0.11+rubygem-rexml-3.2+rubygem-rspec-3.10+rubygem-rspec-core-3.10+rubygem-rspec-expectations-3.10+rubygem-rspec-mocks-3.10+rubygem-rspec-support-3.10+rubygem-vagrant_cloud-3.0+rubygem-webrick-1.7+rubygem-winrm-2.3+rubygem-winrm-elevated-1.2+rubygem-winrm-fs-1.3+vagrant+vagrant-libvirt
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742
Bj�rn Voigt bjoernv@arcor.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bjoernv@arcor.de
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742 http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c28
--- Comment #28 from Luciano Santos luc14n0@opensuse.org --- I've tested here on my Tumbleweed system, using a dummy package to echo output messages. It's working for transfiletriggerin but, sadly, it gets invoked way too frequently IMO.
In a DUP transaction with 377 updates, transfiletriggerin got invoked around 76 times. And transfiletriggerpostun still no joy.
$ rpm -q rpm rpm-4.17.1.1-2.1.x86_64
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742 http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c29
Michael Andres ma@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(mls@suse.com) |
--- Comment #29 from Michael Andres ma@suse.com --- (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
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742 http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c30
--- Comment #30 from Luciano Santos luc14n0@opensuse.org --- (In reply to Michael Andres from comment #29)
(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.
http://bugzilla.opensuse.org/show_bug.cgi?id=1041742 http://bugzilla.opensuse.org/show_bug.cgi?id=1041742#c31
--- Comment #31 from Michael Andres ma@suse.com --- (In reply to Luciano Santos from comment #30)
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.
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com