We now have some better confidence that the failure is purely test-suite
based, and shouldn't affect the operation of the binary itself. Marking
won't fix and leaving the armhf tests disabled until such time as they
can be fixed properly (or removed).
** Changed in: mtd-utils (Ubuntu)
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
$ reverse-depends src:mtd-utils
Reverse-Recommends
==
* 0x [armhf](for mtd-utils)
* python3-binwalk (for mtd-utils)
Reverse-Depends
===
* flash-kernel [arm64 armhf](for mtd-utils)
Packages without architectures listed are
Additional context:
flash-kernel has several methods of "flashing" boot artifacts
(bootloaders, kernel, initrd, etc.) on various boards. Flashing may
actually mean flashing EEPROM (typically done via some other utility, in
many cases mtd-utils -- mtd incidentally is "Memory Technology Device",
