On Sat, 16 Mar 2019, Brett Gilio wrote:
I can replicate this bug, however it is still successfully installing a new system configuration. The error printout seems erroneous (pun intended).
Indeed, I also do get a new system configuration reflecting my changes. However, I'm not sure if the output is just erroneous of if grub is really failing to be installed. By that I mean that the grub-install call is failing, resulting in this output. Since grub has been previously installed to my disk, most of the time I don't need to install the bootloader binary again, so this failure doesn't cause problems.
I am sure there is a regression somewhere, but it does not seem to adversely effect the method in question.
I wonder if Ludovic's recent work [0][1] on handeling the bootloader messages could be the cause.
[0] 22f95e028f038cee342f455dfc55bd32b804907c [1] f0cc5e7e1e4c03af29c5d4855dc5962502c49147
