From Fedora Project Wiki
When updating from a systemV to a systemd package, we "start-over fresh" with default start and stop policy from the package, not what the user had previously configured. systemd provides a tool, systemd-sysv-convert --apply
, to help do this conversion if the user wants after the package is updated.
Scriptlets:
Start over fresh
# This is actually needed for the %triggerun script but Requires(triggerun) # is not valid. We can use %post because this particular %triggerun script # should fire just after this package is installed. Requires(post): systemd-sysv ### A sysv => systemd migration contains all of the same scriptlets as a ### systemd package. These are additional scriptlets # Note: the NEVR in trigger scripts should all be the version in # which the package switched to systemd unit files and the comparision # should be less than. Using <= the last version with the sysV script won't # work for several reasons: # 1) disttag is different between Fedora releases # 2) An update in an old Fedora release may create a newer NEVR # Note that this means an update in an older Fedora release must be NEVR # lower than this. Freezing the version and release of the old package and # using a number after the disttag is one way to do this. Example: # httpd-1.0-1%{?dist} => httpd-1.0-1%{?dist}.1 %triggerun -- httpd < 1.0-2 # Save the current service runlevel info # User must manually run systemd-sysv-convert --apply httpd # to migrate them to systemd targets /usr/bin/systemd-sysv-convert --save httpd # If the package is allowed to autostart: /bin/systemctl enable apache-httpd.service >/dev/null 2>&1 # Run these because the SysV package being removed won't do them /sbin/chkconfig --del httpd >/dev/null 2>&1 || : /bin/systemctl try-restart apache-httpd.service >/dev/null 2>&1 || : /bin/systemctl daemon-reload >/dev/null 2>&1 || :
Subpackage with sysv initscripts
# If we're shipping sysvinit scripts %triggerpostun -n httpd-sysvinit -- httpd < 1.0-2 /sbin/chkconfig --add httpd >/dev/null 2>&1 || :