Juju packaging for xenial must depend on everything in the archive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Xenial |
Fix Released
|
Critical
|
Unassigned |
Bug Description
As part of acceptance into main for juju2, we need to ensure our package depends on everything we can that is already in the archive. See bug 1545913 for the FFe.
This bug will track our dependencies to ensure we meet this requirement.
In archive:
golang-
golang-
golang-
golang-go-dbus-dev
golang-
golang-
golang-
golang-
golang-
golang-
golang-
golang-
golang-check.v1-dev
golang-
golang-
golang-
golang-goyaml-dev
golang-yaml.v2-dev
golang-
golang-
golang-
Packages in Main:
golang-
golang-
golang-go-dbus-dev
golang-
golang-
golang-
golang-
golang-check.v1-dev
golang-yaml.v2-dev
golang-
golang-
golang-
MIRs:
golang-
golang-
golang-
golang-
golang-
golang-
golang-
golang-
golang-goyaml-dev
Changed in juju-core (Ubuntu): | |
importance: | Undecided → Critical |
status: | New → Triaged |
description: | updated |
description: | updated |
description: | updated |
Changed in juju-core (Ubuntu Xenial): | |
status: | Triaged → Fix Released |
Changed in juju-core (Ubuntu): | |
status: | Triaged → Fix Released |
Packaging has been updated and tested with all packages in main. Juju in xenial should depend on the packages in main listed above with the next upload.