The attaches diff shows the changes to the juju embedded dependencies.

** Description changed:

  Juju 2.0 will be in xenial. We want to place juju 2.0-beta2 (or possibly
  beta3) in xenial for Ubuntu users to test.
  
- Juju 2.0 uses a new package name, juju2. This package is co-installable
- with juju-core.
+ This branch introduces the juju2 package.
+ 
+     bzr push lp:~sinzui/ubuntu/xenial/juju2/xenial-2.0-beta2
+ 
+ The juju team propose a new juju2 packages that is co-installable with
+ the juju-core package. This allows users to have juju 2.x and 1.x
+ installed on the xenial host. Users can maintain their 1.x envs
+ while creating new Juju 2.x deployments.
+ 
+ This branch is based on
+     lp:~sinzui/ubuntu/xenial/juju-core/xenial-1.25.4
+ Which is stalled. We are waiting for a 1.25.5 released. We want to
+ use this as the base because it minimises the changes in the debian
+ dir.
+ 
+   * New upstream release (Lp: 1560315).
+   * d/control:
+     - Renamed the package juju-core to juju2.
+     - Dropped unneeded juju-local* and juju packages.
+   * d/rules:
+     - Renamed the package to juju2.
+     - Updated rules to 2.x.
+     - Additional path/name changes to support co-installability with
+       the 1.x juju-core package.
+   * d/copyright: Updated per changes to embedded dependencies.
+   * d/tests/*
+     - Updated tests to use juju2 command line.
+     - Replaced local-provider tests with lxd tests.

** Patch added: "xenial-deps.diff"
   
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1560315/+attachment/4607604/+files/xenial-deps.diff

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

Title:
  [needs packaging] juju2 beta is not in xenial

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to