Remove linux-keystone from trusty updates

This is not ideal; once introduced into main in an LTS release, the implication is that the package will receive security updates for the remaining lifetime of the LTS. I believe there were discussions about this at the time the package was added to trusty-updates, though I don't find any documentation for this now.

On the plus side, there is no Supported: field for the linux-keystone entries in the Packages file. On the minus side, there have been quality issues over time with the Supported: metadata in the archive as well as with the ubuntu-support-status tool, so this distinction is not likely to be well understood by users.

Care should be taken in the future to avoid adding packages to main without clear annotation of support committment, so that users are not led to rely on presumed support periods.

In this instance I can see no justification for keeping the package in the archive given the above statement of non-support.

Removed from trusty-updates, trusty-proposed, trusty-security.

I had agreements from people that, regardless of contract renewals, this would be supported for the life of the LTS, as that's what users expect of software in main. This removal comes as a bit of a surprise.

Fix-committed in revno 347 of lp:maas-images.

Hello Dean, or anyone else affected,

Accepted debian-installer into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debian-installer/20101020ubuntu318.42 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Verified that the debian-installer build for trusty-proposed no longer pulls in keystone kernels, nor produces keystone images.

The verification of the Stable Release Update for debian-installer has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package debian-installer - 20101020ubuntu318.42

---------------
debian-installer (20101020ubuntu318.42) trusty; urgency=medium

  * Drop support for removed keystone kernel (LP: #1623090)
  * Move master kernels to 3.13.0-110.
  * Move lts-xenial kernels to 4.4.0-64 (LP: #1625222)

 -- Adam Conrad <email address hidden> Tue, 28 Feb 2017 09:32:13 -0700