[Rpm-maint] [rpm-software-management/rpm] allow file triggers to make transaction fail? (Issue #2581)

[Ludwig Nussel]

I am trying to use file triggers to perform actions when a kernel gets installed. Ie copy the kernel into the ESP and create boot entries. It could happen that the ESP runs out of space. In that case the system would not boot. In a traditional system one would be doomed anyway. In a transactional system however the system to boot next gets prepared as snapshot in a chroot. So that snapshot can just be thrown away when it can't be made bootable (in fact if anything goes wrong, such as rpm scriptlets).
Unfortunately AFAICT the return value of file triggers is ignored, see https://github.com/rpm-software-management/rpm/blob/33bc736185b6929d9c61678843729ce51833365d/lib/transaction.c#L1876

So we never know whether the transaction had any failures in file triggers. In fact according to the code no post transaction scriptlets and neither plugins can make `rpmtsRun()` fail. Is there a reason for that resp any chance to change that?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2581
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/issues/2581 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20230725/8ccd2a08/attachment-0001.html>