Bug#870513: stretch-pu: package cloud-init/0.7.9-2
Control: tag -1 moreinfo
On Sat, Aug 26, 2017 at 10:56:16 +0200, Thomas Goirand wrote:
> On 08/06/2017 07:12 PM, Jonathan Wiltshire wrote:
> > Control: tag -1 moreinfo
> >
> > On Wed, Aug 02, 2017 at 08:45:57PM +0200, Thomas Goirand wrote:
> >> diff -Nru cloud-init-0.7.9/debian/cloud-init.NEWS cloud-init-0.7.9/debian/cloud-init.NEWS
> >> --- cloud-init-0.7.9/debian/cloud-init.NEWS 1970-01-01 01:00:00.000000000 +0100
> >> +++ cloud-init-0.7.9/debian/cloud-init.NEWS 2017-08-02 20:28:11.000000000 +0200
> >> @@ -0,0 +1,8 @@
> >> +cloud-init default behavior from upstream is to manage sources.list for Debian,
> >> +adding contrib and non-free by default. This is clearly a bug which we have
> >> +fixed. If you need contrib and non-free on your computer running cloud-init,
> >> +then please use /etc/apt/sources.list.d facility, instead of the general file
> >> +in /etc/apt/sources.list, as we changed the behavior. Our appologies for this
> >> +change.
> >> +
> >> + -- Thomas Goirand <zigo@debian.org> Wed, 02 Aug 2017 20:28:11 +0200
> >
> > Is NEWS the appropriate place for this, or would README or the changelog be
> > better? As it will only be shown when upgrading existing systems, this will
> > simply be noise (those systems will already have a sources.list).
> >
> >
> > Thanks,
>
> Hi,
>
> I have removed the README.Debian file, and re-uploaded to:
Why? The contents of that README seem harmless, and Jonathan's question
was about the change in this specific update, and the NEWS file, not
README.Debian.
TBH I'm not sure a behaviour change like this is appropriate for stable,
although it can be argued that people won't deploy it without testing
first. Is the behaviour configurable somehow?
Cheers,
Julien
Reply to: