Comment 8 for bug 772264

On 29 April 2011 05:38, Loïc Minier <email address hidden> wrote:
> @James: qemu-img is actually needed when creating an image file, not
> specifically on !armel; it seems the code testing for qemu-img shouldn't
> be under "if not is_arm_host()".  We could refactor the code to test for
> qemu-img once we know whether we're working on an image file.  (Your
> backwards analysis of why Recommends are not arch-specific would be
> correct for qemu-user-static BTW  :-)
>
> @Marcin: once you remove Recommends, you're on your own; in this case,
> you removed a Recommends which is required for image files, but isn't
> required to write directly to a SD/MMC.  I recommend you install
> Recommends.  The lack of command-not-found on your system also renders
> the failure mode rather cryptic, but again, this is due to you chosing
> not to install Recommends (and living with the resulting failures).
>
> In the future, linaro-image-tools might drop support for the --mmc mode
> of operation where it directly writes to a device, so it would make
> sense to bump qemu-kvm to a Depends for qemu-img or to use something
> else, it's actually not that great to require qemu-kvm for simple
> functionality that dd can provide.

What would replace --mmc? I've been using linaro-image-tools-android
and that option is pretty handy.

>
> --
> You received this bug notification because you are a member of Linaro
> Maintainers, which is subscribed to Linaro Image Tools.
> https://bugs.launchpad.net/bugs/772264
>
> Title:
>  linaro_media_create.utils.UnableToFindPackageProvidingCommand: Cannot
>  lookup a package which provides qemu-img
>