@nacc There are two ways to interpret your question :-) and both are valid inquiries with regards to regression potential, so I'll just check and answer both.
Just now I performed the following steps: 1. Purged the supervisor package, 2. removed the PPA `nacc/lp1594740', 3. ran `apt-get update', 4. ensured the symbolic link /etc/systemd/system/multi-user.target.wants/supervisor.service doesn't exist (indeed it doesn't, as expected), 5. reinstalled the supervisor package from Ubuntu's official repository (verified using `apt-cache policy supervisor'), 6. checked if the Supervisor daemon was started (it wasn't, because I just installed the buggy package), 7. reactivated the PPA `nacc/lp1594740', 8. ran `apt-get update && apt-get install supervisor', this upgraded the supervisor package to the version from the PPA. After step 6 the Supervisor daemon is not running, but after step 8 it is running. Theoretically there could be users out there who never noticed that Supervisor wasn't running after installation and after the upgrade to your fixed package Supervisor would `suddenly' be running for the first time on their system. But of course the whole point is for Supervisor to be running after installation! So this seems good to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594740 Title: Supervisor not enabled or started in Ubuntu 16.04 after installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/supervisor/+bug/1594740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
