group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1614724@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package juju-core - 2.0.0-0ubuntu0.16.04.2

---------------
juju-core (2.0.0-0ubuntu0.16.04.2) xenial; urgency=medium

  * DPKG_MAINTSCRIPT_ARCH doesn't work in .config, use dpkg check (LP:
#1614969)

 -- Nicholas Skaggs <nicholas.skaggs@xxxxxxxxxxxxx>  Mon, 31 Oct 2016
15:55:49 -0400

** Changed in: juju-core (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1614724

Title:
  Juju isn't protected from new versions of LXD

Status in juju-release-tools:
  Fix Released
Status in juju-core package in Ubuntu:
  Fix Released
Status in juju-core source package in Xenial:
  Fix Released
Status in juju-core source package in Yakkety:
  Fix Released

Bug description:
  Juju's autopkgtests don't execute when a new version of LXD is
  uploaded. This means a breaking change uploaded into LXD isn't caught
  before LXD lands.

  This is because juju 2.0 doesn't depend on LXD directly, but instead
  lists it as a recommends. The juju-1 package, juju-local, depends on
  lxc directly and therefore the autopkgtests run during each new lxc
  upload. However, we are vulnerable for 2.0. Juju's autopkgtests do
  cover LXD and would provide protection if they were run.

  To fix, we could list LXD as a depends on a package juju-core source
  package creates. This would run our tests and block incompatible LXD
  changes. Alternatively, we can explore ideas about checking proposed
  ourselves; however, the upload will not be blocked apart from a
  failing autopkgtest.

  
  [SRU Information]

  [Impact]
  The addition of a dependency of LXD ensure juju binaries can only be built on platforms that also can build LXD and publish a package.

  [Verification]
  The debian control field lists LXD as a dependency. We should also see new adt runs of juju when LXD is uploaded.

  [Regression Potential]
  None.

  [Other]
  This should have no impact on end users of the package; the verification can be done by viewing juju-core source upload.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-release-tools/+bug/1614724/+subscriptions