Bug#989645: /usr/sbin/grub-mkconfig: dpkg: error processing package linux-image-powerpc (--configure):

[Rick Thomas]

On Wed, Jun 9, 2021, at 3:15 AM, John Paul Adrian Glaubitz wrote:
> Control: severity -1 normal
> 
> Hello Rick!
> 
> On 6/9/21 11:15 AM, Rick Thomas wrote:
> > Package: grub-common
> > Version: 2.04-18
> > Severity: grave
> > File: /usr/sbin/grub-mkconfig
> > Justification: renders package unusable
> 
> Since powerpc is not a release architecture, setting the severity to 
> "grave" is not
> allowed here. I am therefore downgrading this to "normal".
> 

Got it.  Thanks for the info!

> > This is what happens when I attempt to do "aptitude full-upgrade" on my PowerPC machine:
> > 
> > root at dillserver:/home/rbthomas# aptitude full-upgrade
> > The following partially installed packages will be configured:
> >   linux-image-5.10.0-7-powerpc linux-image-powerpc 
> > No packages will be installed, upgraded, or removed.
> > 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> > Need to get 0 B of archives. After unpacking 0 B will be used.
> > Setting up linux-image-5.10.0-7-powerpc (5.10.40-1) ...
> > /etc/kernel/postinst.d/initramfs-tools:
> > update-initramfs: Generating /boot/initrd.img-5.10.0-7-powerpc
> > /etc/kernel/postinst.d/zz-update-grub:
> > /usr/sbin/grub-mkconfig: 257: cannot create /boot/grub/grub.cfg.new: Read-only file system
> 
> Your HFS filesystem on /boot/grub is read-only. This is not related to GRUB but
> to either your custom environment or something in the partitioning setup in d-i
> that I need to fix.
> 
> Adrian

This happened on two machines (a G5 Mac and a G4 Mac), both of which were originally installed from the respective NETINST-1 iso from 2021-02-02.  For specificity, here are the checksums of the iso images:

9745c507771d6066546146c3d33755ac3b1ca0d4d489647d6a07da38c9612bfc  debian-10.0.0-powerpc-NETINST-1.iso
cf357436e812b50ee8c381abf61c0f7ff634c5bdfd18f4ea8b55a4230a657f00  debian-10.0.0-ppc64-NETINST-1.iso

I have run occasional (roughly weekly) "aptitude update ; aptitude full-upgrade" on each of them since installation.

I did nothing to affect the read-write-ability of /boot/grub on either of them.  So I'm guessing this is a bug you need to fix?

What can I do to help?  (Both of these machines exist at the moment solely to assist in testing your efforts, so I would have no problem re-installing either or both if that would help.)

Thanks for all your work!
Rick