On Wed, Oct 09, 2019 at 06:04:39AM +0000, Dridi Boukelmoune wrote:
On Tue, Oct 8, 2019 at 6:45 PM Ravindra Kumar via devel
<devel(a)lists.fedoraproject.org> wrote:
>
> Hi,
>
>
>
> I have removed dependency on service B from service A and all references to service
B. The new package works well for fresh install (service A can be started normally), but
it does not work for upgrades from previous versions where service A used to depend on
service B (starting service A fails as it can’t fine the service unit for service B).
After upgrade from a previous version of the package, I noticed that a symlink to service
B is left under /etc/system/system/A.service.requires dir that is causing the issue:
>
> # ls -l /etc/systemd/system/A.service.requires
>
> total 0
>
> lrwxrwxrwx. 1 root root 45 Oct 8 11:10 B.service ->
/usr/lib/systemd/system/B.service
>
>
>
> Basically, some cleanup is needed to remove the requires symlink that is no longer
needed.
You need something like this in a scriptlet:
if systemctl is-enabled A; systemctl reenable A; done
This will remove the old links and create the new ones.
> > Any advice/examples of such cleanup?
>
> systemctl daemon-reload?
>
> Isn't this handled automatically by the %systemd scriptlets?
>
> Dridi