[Rpm-maint] [rpm-software-management/rpm] Changes to transaction file triggers to make them viable for systemd (Discussion #4016)
Daan De Meyer
notifications at github.com
Sun Nov 2 09:51:34 UTC 2025
So I'm trying to get something working with the existing functionality using postun file triggers. Weird behavior that I'm seeing with those:
1. On upgrade, both the trigger of the old and the new version run:
```
>>> Running %triggerpostun scriptlet: systemd-0:259~devel-20251102094054.fc43.x86_64
>>> Finished %triggerpostun scriptlet: systemd-0:259~devel-20251102094054.fc43.x86_64
>>> Scriptlet output:
>>> Removed '/etc/systemd/system/sockets.target.wants/systemd-networkd-varlink.socket'.
>>> Stopping unit 'systemd-networkd-varlink.socket'
>>>
>>> Running %triggerpostun scriptlet: systemd-0:259~devel-20251102094356.fc43.x86_64
>>> Finished %triggerpostun scriptlet: systemd-0:259~devel-20251102094356.fc43.x86_64
>>> Scriptlet output:
>>> Stopping unit 'systemd-networkd-varlink.socket'
>>>
```
2. Unlike the transaction file triggers, the package file triggers do **not** seem to get passed the full list of files in the rpm database on upgrade, even though I would also expect that to happen for package file triggers on upgrade.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/4016#discussioncomment-14849970
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/repo-discussions/4016/comments/14849970 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20251102/62836639/attachment-0001.htm>
More information about the Rpm-maint
mailing list