This bug was fixed in the package juju-core - 1.25.5-0ubuntu3~14.04.1
---
juju-core (1.25.5-0ubuntu3~14.04.1) trusty; urgency=medium
* Backport of juju-core-1_1.25.5-0ubuntu3 to 14.04 (Lp: #1556981).
* As the packages were renamed to juju-core-1 and juju-1, most changes
to d/
This bug was fixed in the package juju-core - 1.25.5-0ubuntu3~15.10.1
---
juju-core (1.25.5-0ubuntu3~15.10.1) wily; urgency=medium
* Backport of juju-core-1_1.25.5-0ubuntu3 to 15.10 (Lp: #1556981).
* As the packages were renamed to juju-core-1 and juju-1, most changes
to d/
** Description changed:
Juju 1.25.5 enables maas 1.9, and several AWS instance types and
regions. It included fixes many bugs reported against 1.24.7
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
The juju-qa team tests of 1.25.5-0ubuntu3~14.04.1 in trusty-proposed
pass.
The juju is compatible with the agents in streams. It is fit for cloud
deployments.It is suitable for devel and testing using the local-
provider. the manual-provider can be used in production scenarios. The
juju is
The juju-qa team tests of 1.25.5-0ubuntu3~15.10.1 pass.
The juju is compatible with the agents in streams. It is fit for cloud
deployments. It is suitable for devel and testing using the local-
provider. the manual-provider can be used in production scenarios. The
juju is compatible with the
Hello Curtis, or anyone else affected,
Accepted juju-core into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/juju-
core/1.25.5-0ubuntu3~14.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Curtis, or anyone else affected,
Accepted juju-core into wily-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/juju-
core/1.25.5-0ubuntu3~15.10.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Uploaded to Trusty and Wily. Nothing to flag on review - thanks Curtis.
I did note that debian/copyright is different (presumably updated, based
on your changelog message?) in your backports when compared to
debian/copyright in src:juju-core-1 in Yakkety. Not worth blocking an
SRU, but please
Thank you also for the git trees. This saved me a ton of time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556981
Title:
[needs-packaging] Juju 1.25.5 is not in wily and trusty
To manage
src:juju-core-1 1.25.5-0ubuntu3 is in Yakkety, so notionally Fix
Released but there seems little point to have a task just for that. src
:juju-core is thus Invalid for the development release and needs tasks
for Trusty and Wily.
** Also affects: juju-core (Ubuntu Wily)
Importance: Undecided
** Description changed:
Juju 1.25.5 enables maas 1.9, and several AWS instance types and
regions. It included fixes many bugs reported against 1.24.7
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
^ Both the wily and trusty packages were verified to pass their
respective ADT tests. The repo has the pristine-tar files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556981
Title:
I prepared a backport of juju-core-1 1.25.5-0ubuntu3 for wily.
https://git.launchpad.net/~sinzui/ubuntu/+source/juju-core/log/?h
=ubuntu-wily
This is *not* a no-change backport because the source package was
renamed to juju-core-1 in xenial. Most the the debian/ changes relate to
the rename.
I prepared a backport of juju-core-1 1.25.5-0ubuntu3 for trusty.
https://git.launchpad.net/~sinzui/ubuntu/+source/juju-core/log/?h
=ubuntu-trusty
This is *not* a no-change backport because the source package was
renamed to juju-core-1 in xenial. Most the the debian/ changes relate to
the
14 matches
Mail list logo
