[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#751721: Figure out how to deal with ABI changes

Hi Phillip

On Mon, Jun 16, 2014 at 12:31:25AM +0200, Philipp Kern wrote:
> There are many ways a kernel can be updated on disk that are not
> necessarily triggered by user action.

Debian does not install any automatic update stuff, so it is always user

> Ubuntu claims with every update that there is an unavoidable ABI change.
> I guess that's why. It at least sidesteps this issue if you handle ABI
> changes that way. Of course it also makes d-i more brittle unless you
> keep old ABI versions around and do not decruft them.

Can you provide a course of action to handle this differently?  Please
note that currently an ABI name change involves manual action by at
least five entities (kernel-team, ftp-team, release-team, d-i-team and
external modules maintainers).  If we want to do that in a faster pace,
we need some automation on the way.


Reply to: