fix systemd ordering cycle in quasselcore.service
Previously I changed the service to After=default.target so that
postgresql has a chance to start up, in the case it is used as the
database. This seems to cause an ordering cycle causing the service to
not start on boot.
I am not sure if this was a problem before, or just started happening
with a more recent systemd.
I talked to a knowledgeable person on freenode #systemd (boucman) who
suggested using After=postgresql.service instead, there is no error if
the postgresql.service is not installed. Likewise add
After=mysql.service in case it is the database being used. If sqlite is
being used (as is the default) then After=network-online.target would be
in effect.
OBS-URL: https://build.opensuse.org/request/show/631132
OBS-URL: https://build.opensuse.org/package/show/KDE:Extra/quassel?expand=0&rev=74