[Rpm-maint] broken filetriggers implementation when using a chroot

[Thierry Vignaud]

On 6 January 2016 at 12:42, Thierry Vignaud <thierry.vignaud at gmail.com> wrote:
> Sadly, the current filetriggers doesn't honour rpm's chroot.
> Thus it works fine with our rpm front-end (urpmi which is like yum/dns
> for FC) for online updates.
>
> But not with our installer (Drakx) which installs packages in a chroot
> (like Anaconda does for FC)
> See https://bugs.mageia.org/show_bug.cgi?id=17217
> And urpmi can reproduce this too when using a chroot:

The 3 attached patches fix this bug.
I've split them into 3 parts:
- add a new API for package state machine
- use it in psm.c
- fix the remaining issues in transaction.c
  (aka file triggers in _other_ packages)

Please apply.

Patches are against the rpm-4.13.x branch.
When merged in HEAD, there'll be a trivial conflict in the last bit of
the 3rd patch due to
"Add possibility to disable file triggers" commit

Thanks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-runImmedFileTriggersInChroot-introduce-it.patch
Type: application/binary
Size: 2108 bytes
Desc: not available
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20160109/c09bcaa6/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-fix-transfiletrigger-iu-n-file-triggers.patch
Type: application/binary
Size: 1120 bytes
Desc: not available
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20160109/c09bcaa6/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0003-fix-transaction-filetriggers-in-other-package-s.patch
Type: application/binary
Size: 1938 bytes
Desc: not available
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20160109/c09bcaa6/attachment-0002.bin>