Public bug reported:

There's a general desire to be able to drop upstart into universe (or at
least off the default image).  But we still use it in unity8 (and maybe
some of unity7 still?).

I'm trying to investigate the work that needs to be done to make the
conversion complete for unity7/8.  But I wanted to start the
conversation here about such a change this late in the zesty cycle.

The regression potential is real, but testing it should mostly be a
"does the service launch or not."

I'd like to keep shipping upstart files, at the least because our
unity8-session snap will need to keep using it for a bit.  But they will
be disabled with a manual override when using systemd user sessions.

** Affects: ubuntu
     Importance: Undecided
         Status: New

** Description changed:

  There's a general desire to be able to drop upstart into universe (or at
  least off the default image).  But we still use it in unity8 (and maybe
  some of unity7 still?).
  
  I'm trying to investigate the work that needs to be done to make the
  conversion complete for unity7/8.  But I wanted to start the
  conversation here about such a change this late in the zesty cycle.
  
  The regression potential is real, but testing it should mostly be a
  "does the service launch or not."
  
  I'd like to keep shipping upstart files, at the least because our
- unity8-session snap will need to keep using it for a bit.
+ unity8-session snap will need to keep using it for a bit.  But they will
+ be disabled with a manual override when using systemd user sessions.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675168

Title:
  [FFe] Using systemd user units instead of upstart jobs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1675168/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to