http://bugzilla.suse.com/show_bug.cgi?id=1090785
http://bugzilla.suse.com/show_bug.cgi?id=1090785#c4
--- Comment #4 from Franck Bui
I think a combination of https://build.opensuse.org/package/rdiff/Base:System/systemd-rpm- macros?linkrev=base&rev=26 and https://build.opensuse.org/package/rdiff/Base:System/systemd-rpm- macros?linkrev=base&rev=28 means that %systemd_user_post has gone from error+doing nothing (42.3) to applying presets (Leap 15.0), whether intentional or not.
Thanks for the details, this makes sense.
I have no idea if many other packagers are using %systemd_user_pre/post(un). They *are* part of Fedora package guidelines. I used them expecting stop on removal and presets as for system services.
Basically the SUSE specific macros %service_{add,del}_* have been introduced before the ones shipped by upstream (%systemd_*). They also support a corner case that the upstream versions don't: when a SysV service is converted into a systemd one (during a package update) the systemd service should still be left enabled/disabled if the SysV service was enabled/disabled. That said if your package has never shipped SysV init scripts, the upstream version should be fine and should be more portable accross (rpm based) distros. -- You are receiving this mail because: You are on the CC list for the bug.