On Sat, Jun 24, 2017 at 09:17:38PM +0900, Norbert Preining wrote:
> Very interesting - thanks for pointing me at that. When I switched
> the packages to triggers there was no "noawait" version (AFAIR), and
> I haven't reviewed the status till now.
The dpkg maintainers wants to start deprecating the original trigger
that are implicitly "await" to bring more awareness in this field.
Besides, "await" triggers have the potential to cause the dreaded
"trigger cycles" that can cause upgrades to fail and can be very hard to
fix (a trigger cycle was found in a very common upgrade path the week
before the stretch release, and there was even talking of delaying the
release at that time!).
> That sounds definitely like a good option, as one call at the very end
> would suffice completely!
I guessed so :)
> JFMI: I guess the only time a -await (or no -noawait) is necessary
> when the post install action requires the trigger action to be
> executed. Right? In this case I should be able to switch all the
> triggers to -noawait.
Yes, that's one case where -await triggers are needed.
Another would be when the risk of not running the trigger could cause
the system to be in a severely inconsistent state if the upgrade was to
suddenly be interrupted, for example.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Attachment:
signature.asc
Description: PGP signature