Description of problem:
Entry in /usr/lib/systemd/system/abrtd.service causes systemd to show livesys.service error even when livesys disabled/removed.

# livesys.service has been added because of live distributions mounting tmpfs
# to /var/tmp after abrtd.service was started which was hiding /var/tmp/abrt
# which was created before the mount to tmpfs happened
After=livesys.service


Version-Release number of selected component (if applicable):
abrt-2.15.1-6.fc37.x86_64
(This is probably really a systemd problem, 251.11-2.fc37)


How reproducible:
Always unless that line is commented out.

Steps to Reproduce:
1. Remove all trace of livesys after installation (otherwise it generates
other "messages" by just being there & it should be removed right?).
2. systemctl -all |grep livesys
        livesys.service    not-found inactive   dead      livesys.service
3. The "problem" is also manifested by 

Actual results:
Uninstalled systemd objects should not give an error status

Expected results:
The ability to run systemctl -all & see no errors/services in error states,
when you've ironed out all the mysteries & unnecessary components.

Additional info:
It would seem that systemd needs a better system of ordering or checking for unused/installed components that require ordering or "Conflicts=" (which also generate a similar effect.
Or merely "noting silently that an uninstalled/non-conflicting package does not
need to be considered in it's logic" - but that's probably a recipe for more
subtle bugs.

BTW, in the systemctl documentation there is no mention of "Yellow" dots - are
they real in the systemctl output or have I screwed my terminal colour scheme?
It seems they are services that "ain't really there".

Is this too philosophical?