Comment 8 for bug 1574069

Hmm. Does this problem not reoccur every time a new kernel package is installed? Or does it happen only once when upgrading into Xenial?

I'm not sure we should remove the package from the repo, given I think there are valid use cases for it, but perhaps we could make it so installing the Xenial kernel removed it.