http://bugzilla.opensuse.org/show_bug.cgi?id=966057 Juraj Hura <jhura@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jhura@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966057 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |trenn@suse.com, | |zypp-maintainers@forge.prov | |o.novell.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966057 http://bugzilla.opensuse.org/show_bug.cgi?id=966057#c1 --- Comment #1 from Michael Andres <ma@suse.com> --- Unfortunately rpm has nothing like a %postuntrans script, so there's no 'final' trigger for deleted packages after the %postun. What you can try is to execute the action immediately, if '%postun 0' (on final delete) was called (and no trigger has been placed by now). If the 1st arg is not 0 (upgrade), the newly installed packages %posttrans will do the job. Not perfect, but maybe better than nothing. -- You are receiving this mail because: You are on the CC list for the bug.

Unfortunately rpm has nothing like a %postuntrans script, so there's no 'final' trigger for deleted packages after the %postun. The issue with a %postuntrans is that the script can't depend on anything,

http://bugzilla.opensuse.org/show_bug.cgi?id=966057 http://bugzilla.opensuse.org/show_bug.cgi?id=966057#c2 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fvogt@suse.com) | --- Comment #2 from Fabian Vogt <fvogt@suse.com> --- (In reply to Michael Andres from comment #1) literally. It could be that someone ran "zypper rm glibc" or similiar, so practically any script would fail. Even the script interpreter might be gone...

What you can try is to execute the action immediately, if '%postun 0' (on final delete) was called (and no trigger has been placed by now). If the 1st arg is not 0 (upgrade), the newly installed packages %posttrans will do the job.

Not perfect, but maybe better than nothing.

Definitely better than nothing and also what I did for plymouth in my home repo. Issue is that this can cause mkinitrd to run multiple times during a transaction and it also looks like it's stuck somewhere as it stays at a certain percentage for quite a while, depending on how many kernels are in /boot. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966057 http://bugzilla.opensuse.org/show_bug.cgi?id=966057#c4 --- Comment #4 from Fabian Vogt <fvogt@suse.com> --- Ping. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966057 http://bugzilla.opensuse.org/show_bug.cgi?id=966057#c10 --- Comment #10 from Fabian Vogt <fvogt@suse.com> --- (In reply to Cliff Zhao from comment #9)

Hi Fabian:

Thanks for catching this problem. and I notice that you reported this bug as comment0. So I will only discuss with you about this basic problem. and after so many discussions here, if you feels this bug disappear, please close it. if you still want to fix the original problem, please find the right assignee.

It still exists.

and for the Plymouth, if you find anything not good, please open new bug and share me the your reproduce steps and the expect result from the user perspective of view.

If you don't have user level test case, I think I can not guarantee that I will agree to do it.

Steps to reproduce the issue: Install a system with plymouth. After it's booted, zypper rm libply* and reboot again. You'll notice that it still shows the splash screen, which can break the system boot completely. Comment 5 has the right information to fix this. -- You are receiving this mail because: You are on the CC list for the bug.