Bug#929096: marked as done (unattended-upgrades: defaults change to upgrade stable suite)
Your message dated Sat, 18 May 2019 21:41:40 +0200
with message-id <[hidden email]>
and subject line Re: Bug#929096: unattended-upgrades: defaults change to upgrade stable suite
has caused the Debian Bug report #929096,
regarding unattended-upgrades: defaults change to upgrade stable suite
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [hidden email] immediately.)
The version of unattended-upgrades in stretch defaulted to not upgrading
the stable suite. It would install only security updates.
The version of unattended-upgrades in buster upgrades both the stable
suite and security upgrades. I.e. it will pull in point releases too.
There are probably good reasons for this defaults change, but I think it
needs to be documented, either in NEWS.Debian for unattended-upgrades,
and/or (since the package is very widely installed) in the buster
On 17-05-2019 15:49, Justin B Rye wrote:
> <section id="unattended-upgrades">
> <!-- stretch to buster -->
> <title>Unattended-upgrades for stable point releases</title>
> Previous versions of <systemitem
> role="package">unattended-upgrades</systemitem> defaulted to installing
> only upgrades that came from the security suite. In buster it now also
> automates upgrading to the latest stable point release. For details, see
> the package's NEWS.Debian file.