After carefully rereading @nacc's question I realized I missed an
essential detail ("does it end up using the same systemd file"). I
believe this is indeed the case, as intended (I assume?).Here's what I get after a clean install of the fixed package: peter@mbp> ls -ld /etc/systemd/system/multi-user.target.wants/supervisor.service lrwxrwxrwx 1 root root 38 Mar 13 23:53 /etc/systemd/system/multi-user.target.wants/supervisor.service -> /lib/systemd/system/supervisor.service Here's what I get after upgrading from the buggy version to the fixed version: peter@mbp> ls -ld /etc/systemd/system/multi-user.target.wants/supervisor.service lrwxrwxrwx 1 root root 38 Mar 13 23:55 /etc/systemd/system/multi-user.target.wants/supervisor.service -> /lib/systemd/system/supervisor.service The target of the symlink is the same in both cases. The timestamps differ but that's just the creation time of the symlink AFAIK (from the moment 'systemctl enable' or an equivalent command is invoked). -- 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
