Bug#930058: unblock: puppet/5.5.10-3
On Mon, Jun 17, 2019 at 12:59:10AM +0200, Thomas Goirand wrote:
> I don't think people read more the NEWS than the changelog.
I'm not sure how you arrive at that conclusion, but here's a consideration:
it's my company's policy that the NEWS are read during every upgrade of a
client system (and our own) to catch surprises like this. It is a good
example of exactly what NEWS files are for.
Popcon also suggests that 85% of respondents have apt-listchanges
installed, which is the package giving this behaviour.
So I disagree with your statement that it is a waste of time documenting a
surprising behaviour change like this. As Micah demonstrates, local
administrators upgrading may already have a mechanism to deal with the
problem and your cron job will conflict with that.
> Having run puppet on a small virtual machine with 40 GB disk, and having
> it taken down by 800 MB reports every day for every compute in the
> cluster, no, this isn't controversial. This is completely mandatory.
> What I believe puppet user do is set this up by themselves, or disable
> reports all together. Keeping 1 month of reports is very conservative.
I don't disagree with the problem statement.
Thanks,
--
Jonathan Wiltshire jmw@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
Reply to: