Comment 3 for bug 2061990

Potentially affected images:

As noted above this potentially affects *any* armhf image with boot artifacts that require flashing (that are deb based). This potentially affects our older Pi server armhf images (which, although they don't use mtd-utils, do use flash-kernel). However, we're not producing Pi server armhf images this cycle and it is my understanding that do-release-upgrades has a quirk to prevent upgraders on that architecture.

It does not affect our Pi desktop images, which have never been armhf based.

This change potentially affects any flavours which produce such images. However, there has never (to my knowledge) been an official flavour with an armhf desktop image for the Pi.

Further mitigation ideas:

flash-kernel *could* be modified to merely recommend mtd-utils and still operate on platforms where mtd-utils itself isn't used for flashing boot artifacts (such as the Pi) but obviously this complicates the dependency situation (and seeds) on those platforms that *do* require mtd-utils.