Comment # 3 on bug 1192011 from Raymund Will

From my PoV this issue can be solved in two ways:

#1 change `shim` to require the proper grub-platform for the
architecture it is built for and not the generic `grub2-efi`
(which was IMHO obsoleted by the noarch-move in FATE#326960).

This may take a considerable amount of time, depending on whether
repackaging of `shim` will require a new M$ signature or not.

#2 amend the image definition, that pulls in `shim`, to also
request the grub2-platform package (`grub2-x86_64-efi` in this
case), to avoid the BS ambiguity.

Robert, would #2 be a viable option?