trusty-mitaka disabled, pending upstream crit bug fix and subsequent packaging

[Ryan Beisner]

During initial development of the barbican-* charms, upstream issues were discovered and patches proposed. To unblock dev, the charms temporarily install the packages from this PPA, which only builds Xenial.

https://launchpad.net/~ajkavanagh/+archive/ubuntu/barbican

Follow-up actions needed:

1. Once the upstream fix lands, and exists in the xenial packages and trusty-mitaka cloud archive packages, the charms should be adjusted to no longer use the PPA.

2. After [1], the charms should also undergo validation and ci-enablement for trusty-mitaka.

[Ryan Beisner (1chb1n)]

Alternatively, while waiting for upstream bugfix and the packaging bits, we could enable Trusty package builds in that temporary PPA and enable trusty-mitaka for CI and charm series pushes.

[Corey Bryant (corey.bryant)]

Ryan, The PPA use was dropped in the following commit. Can we close this bug out?

commit aa47fd5b0eda12afebdf301ce91cee287841df4d
Author: Alex Kavanagh <email address hidden>
Date: Wed Aug 31 19:35:36 2016 +0000

    Refactor charm to work with declarative-changes

    This is a refactor of the charm (no new functionality) to work with the
    declarative helpers in charms.openstack. This means that much of the
    boiler plate has disappeared from the charm and into charms.openstack
    including the tests.

    Change-Id: I4305eb34f314f8f5f1a7d1807508bf1e4dbfb84c
    Depends-On: I3c74f60bb4ed7901828902118697f310622c4061
    Depends-On: Ic81e65f5a072f67cbd2322e4cfd0eec9a5895823