* New upstream snapshot.
* add ability to configure Acquire::http::Pipeline-Depth via
cloud-config setting 'apt_pipelining' (LP: #942061)
* if cloud-config settings removed default certificats
(remove-defaults), then seed package ca-certificates to not
install new ones on upgrade.
* run-parts now uses internal implementation rather than
separate command.
* add MaaS datasource (LP: #942061)
* debian/cloud-init.postinst: address population of apt_pipeline
setting on installation.
* debian/cloud-init.postinst: support configuring cloud-init
maas datasource via preseed values cloud-init/maas-metadata-url and
cloud-init/maas-credentials. (LP: #942061)
* debian/cloud-init.postinst: support for (LP: #924375)
-- Scott Moser <email address hidden> Fri, 09 Mar 2012 16:37:01 -0500
This bug was fixed in the package cloud-init - 0.6.3~bzr539- 0ubuntu1
--------------- bzr539- 0ubuntu1) precise; urgency=low
cloud-init (0.6.3~
* New upstream snapshot. :http:: Pipeline- Depth via remove- defaults) , then seed package ca-certificates to not cloud-init. postinst: address population of apt_pipeline cloud-init. postinst: support configuring cloud-init maas-metadata- url and init/maas- credentials. (LP: #942061) cloud-init. postinst: support for (LP: #924375)
* add ability to configure Acquire:
cloud-config setting 'apt_pipelining' (LP: #942061)
* if cloud-config settings removed default certificats
(
install new ones on upgrade.
* run-parts now uses internal implementation rather than
separate command.
* add MaaS datasource (LP: #942061)
* debian/
setting on installation.
* debian/
maas datasource via preseed values cloud-init/
cloud-
* debian/
-- Scott Moser <email address hidden> Fri, 09 Mar 2012 16:37:01 -0500