Here is the changelog for the package I'm asking SRU for:
juju-core (1.22.1-0ubuntu0.14.04.1) trusty; urgency=medium
* New upstream release (LP: #1444037).
* Packaging changes required by the new release and cherry-picked from Vivid:
- d/tests/fake-future.sh: New ability to generate fake /etc/os-release.
Change is needed to provide Juju 1.22.1 with an appropriate testbed.
- d/control: Juju-local now depends on cloud-image-utils | cloud-utils.
Juju uses ubuntu-cloud template which in turn uses cloud-image-utils.
Package lxc-templates only recommends cloud-image-utils hence Juju needs
to require this package directly. Package cloud-utils is mentioned as an
alternative because cloud-image-utils is not available on precise but we
want to unify Juju packaging for all supported releases.
- d/copyright: Updated to reflect changes in the codebase.
* Compliance to Debian Policy 3.9.6 was declared.
Few comments about the changes:
(1) d/tests/fake-future.sh change is absolutely required by the new
release. Without this change future-local-provider and future-manual-
provider autopkgtests fail. These tests check if Juju can live inside
new development release (when version and codename change) and proposed
change extends emulation layer by generating fake /etc/os-release. Juju
didn't process /etc/os-release before hence we need this change only for
1.22+.
(2) d/control change has been cherry-picked from Vivid because (a) not
fixing this bug will lead to issues with juju when lxc-templates package
have been installed w/o recommends (b) we want to minimize packaging
delta between supported releases.
(3) d/copyright change is needed because code base changed and we have
to react by providing up-to-date d/copyright. It also helps to minimize
packaging delta.
(4) Compliance to Debian Policy 3.9.6 has been declared to minimize
packaging delta. I don't see any regression potential here.
We still have some delta between 1.22.1 in Vivid and Trusty:
(1) Version in Trusty has explicit build dependency on libgo5 (>=
4.9.1-0ubuntu1) [!amd64 !i386 !armhf]
This change addressed the following issue:
https://bugs.launchpad.net/juju-core/+bug/1377325
While 4.9.1-0ubuntu1 is the current version of the package in Trusty I don't
see any reason to remove this explicit versioned dependency. It minimizes SRU
delta and potential regression risk.
(2) Version in Vivid have autopkgtests modified to revert back to
upstart before running tests. This is needed because Juju 1.22.* doesn't
support systemd which is default init system in Vivid. This delta will
be removed with Juju 1.23 release which supports systemd.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1444037
Title:
juju-core 1.22.1 is not packaged in Ubuntu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1444037/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
