Hello, Can you specify which packages are the A & B? I wanted to reproduce the initial situation - that the service requiring another will put a symlink to the "/usr/lib/systemd/system". I forged iptables RPM containing service file mentioning "Requires=firewalld.service" to see the link to be created, but it wasn't. (iptables because it builds fast and firewalld because it is already installed) I wanted to run audit on the location to catch a process which would create the symlink, in a hope that it won't be systemd itself, but rather some systemd helper script, which name would be good starting point for google. ( "auditctl -w /etc/systemd/system/" and "ausearch -f /etc/systemd/system/" ) -- Michal Schorm Software Engineer Core Services - Databases Team Red Hat -- On Sat, Oct 12, 2019 at 8:12 AM Ravindra Kumar via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > > 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. > > Thanks Zbigniew for the idea. It seemed very promising and I tried it. Unfortunately, it still did not help because "reenable" command seems to recreate the links based on the service unit file which is newer and does not reference the dropped dependency. So, the old link to service B was still left around. > > The only working solution I have found is to disable service B explicitly in post install scriptlet when it is called during upgrade. > > Thanks, > Ravindra > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
