Buhuu... pk 1.0.10 checks if /system-update points to /var/cache/PackageKit (where it would expect the rpms to reside); if not, it's meant to not do the update, as it would indicate 'something else prepared for the update'. we do not provide the /var/cache/PackageKit directory. as we do not store the RPMs there.. hence, the /system-update symlink is dangling, resulting in pk-offline-update claiming the triggers were not set (REBOOT action not being set) pk-offline-update later on verifies if the symlink points to /var/cache/PackageKit (without caring if the target exists) and if it does, it applies the patches... The easiest fix for us is to just provide an empty directory /var/cache/PackageKit I guess.