On Tue, Oct 23, 2018 at 10:05:35PM +0200, Tollef Fog Heen wrote: > > To be clear, the ongoing cost to the cloud team of dealing with jessie > > on AWS (where this issue originally came up) has been exactly zero, > > afaict. That is, we haven't actually updated anything in >18 months. > > Users who launch a jessie image there get 8.7, with 106 pending updates. > > As long as LTS exists and users are happy with it, there's nothing > > strictly wrong with this situation. They should update their instances > > and reboot, but from there, they are free to continue using them in > > relative safety. > > I disagree with the statement that there's nothing wrong with this. Sorry; to be more precise, I meant that there's nothing wrong that can't be remedied using entirely standard and well-established workflows, e.g. dist-upgrade. There's no need to add custom apt sources, apt keys, or anything like that. dist-upgrade is something I'd expect most users to do pretty early in the lifetime of a cloud instance (and possibly regularly after that, depending on how long it's expected to remain active). noah
Attachment:
signature.asc
Description: PGP signature