[Bug 1416051] Re: juju-core 1.22.0 is not packaged in Ubuntu

[Oleg Strikov]

Juju 1.22.0 can't provision instances which run vivid because it doesn't
support systemd. Systemd support has been introduced in Juju 1.23 and we
plan to package this release when it becomes stable (now in beta).
However, I think that having 1.22 in vivid is much better than having
Juju 1.20 (what we currently have) taking into account that 1.20 doesn't
support vivid as well. We get new features of Juju 1.22 and can use them
against trusty and precise instances.

Due to the fact that Juju 1.22 can't provision instances which run vivid, many dep8 autotests fail. These tests rely on juju local provider (LXC) and expect to have upstart running on both host machine and guest instance. I made decision to avoid modifying tests because this operation is needed only for 1.22 and will be reverted while packaging 1.23. To do functional testing I modified the image adt-run uses and manually installed upstart there. Then, I run adt-run and get all tests passed:
http://paste.ubuntu.com/10760926/
I think that this can be counted as equivalent to the regular autotests run which is carried out automatically against package in -proposed.

Curtis Hovey (sinzui) from Juju Team carried out all the testing
procedures required (see #2) and we are ready to move juju-1.22.0
package from -proposed to release. This can't be done automatically
(dep8 tests fail) that's why I'm asking for sponsorship to *manually*
move the package to release repo.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1416051

Title:
  juju-core 1.22.0 is not packaged in Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1416051/+subscriptions