
On Mon, 2020-12-14 at 11:19 +0100, Dan Čermák wrote:
Olaf Hering <olaf@aepfle.de> writes:
Did anyone already explore the potential pitfalls of moving "restart on update" from %postun to %posttrans?
There is one catch: if there are %posttrans scriptlets in a package, then libzypp will invoke rpm with `--noposttrans` [1] which also prevents %transfiletrigger scriptlets from firing. Zypper then invokes the collected posttrans scriptlets after the transaction, but it never invokes the transaction file triggers.
Which is why we do not accept transfiletriggers in Factory (except vagrant - where somehow it was missed) as zypp installs every RPM as an own transaction, in any case, transfiletrigger reacts exactly the same as filetrigger in our cases. The existing triggers can simply be converted at no lose of functionality (well, some loss - if somebody were to install using pure rpm, they might have a benefit; Possibly also if using DNF, not sure exactly how that does the transaction handling in openSUSE) Cheers, Dominique