Re: Straw poll - cloud-init in base AMIs (was Re: cloud-init_0.7.1-3~bpo70+1_amd64.changes ACCEPTED into wheezy-backports, wheezy-backports)
Le Sun, May 05, 2013 at 12:09:10PM +0900, Charles Plessy a écrit :
> One solution would be to add wheezy-backports to /etc/apt/sources.list. By
> default, it will never cause the installation of backports on the system unless
> the administrator specifically requests it. Because wheezy-backports are
> configured with "ButAutomaticUpgrades: yes", security updates for the
> backported cloud-init will come the same way as security updates for packages
> in Wheezy. Apart from the goal of being as similar as possible as systems
> installed with Debian-Installer with default choices, I do not see
> disadvantages for doing so.
Note as well that having backports enabled by default has already been
requested (http://bugs.debian.org/691651) and discussed (on debian-devel in
March), and that there was no critical objection. So if we set up the bar too
high in terms of reducing the differences between cloud images and standard
installations, we will lock ourselves in a situation where we do not enable
backports because there is no momentum on #691651, and where we can not give
momentum to #691651 because we do not enable backports for ourselves.
I propose to move forward and enable backports by default.
Tsurumi, Kanagawa, Japan