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

2021-06-09 Thread Rick Thomas
Package: grub-common
Version: 2.04-18
Severity: grave
File: /usr/sbin/grub-mkconfig
Justification: renders package unusable
X-Debbugs-Cc: debian-powerpc@lists.debian.org, glaub...@physik.fu-berlin.de, 
rbtho...@pobox.com

This is what happens when I attempt to do "aptitude full-upgrade" on my PowerPC 
machine:

root@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
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 2
dpkg: error processing package linux-image-5.10.0-7-powerpc (--configure):
 installed linux-image-5.10.0-7-powerpc package post-installation script 
subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-powerpc:
 linux-image-powerpc depends on linux-image-5.10.0-7-powerpc (= 5.10.40-1); 
however:
  Package linux-image-5.10.0-7-powerpc is not configured yet.

dpkg: error processing package linux-image-powerpc (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-5.10.0-7-powerpc
 linux-image-powerpc
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
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
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 2
dpkg: error processing package linux-image-5.10.0-7-powerpc (--configure):
 installed linux-image-5.10.0-7-powerpc package post-installation script 
subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-powerpc:
 linux-image-powerpc depends on linux-image-5.10.0-7-powerpc (= 5.10.40-1); 
however:
  Package linux-image-5.10.0-7-powerpc is not configured yet.

dpkg: error processing package linux-image-powerpc (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-5.10.0-7-powerpc
 linux-image-powerpc
 
-- Package-specific info:

*** BEGIN /proc/mounts
/dev/mapper/dill-root / ext4 rw,relatime,errors=remount-ro 0 0
/dev/mapper/dill-home /home ext4 rw,relatime 0 0
/dev/sda3 /boot ext2 rw,relatime 0 0
/dev/sda2 /boot/grub hfs ro,relatime,uid=0,gid=0 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_apple
insmod lvm
insmod ext2
set 
root='lvmid/KyeuOm-Fceg-PCoI-LcmV-eVLL-RnL7-Xh0WT4/Ut9qE2-72vC-tTDE-XyVH-6Z0i-GXy3-lyyiCh'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root 
--hint='lvmid/KyeuOm-Fceg-PCoI-LcmV-eVLL-RnL7-Xh0WT4/Ut9qE2-72vC-tTDE-XyVH-6Z0i-GXy3-lyyiCh'
  9151f254-2918-4435-bd1c-9a0e70edfdf7
else
  search --no-floppy --fs-uuid --set=root 9151f254-2918-4435-bd1c-9a0e70edfdf7
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_sty

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

2021-06-09 Thread John Paul Adrian Glaubitz
Hello Rick!

On 6/9/21 11:34 PM, Rick Thomas wrote:
> You're right that /boot/grub somehow has gotten read-only.  I didn't do that
> myself, so something else must have done that.  Have you any clue you can 
> share
> with me as to which package I should re-file this report against?
You are too quick in assuming that there might be a bug somewhere. We don't know
yet how and why the filesystem was re-mounted read-only. You should check your
log files for any error messages or warnings.

Normally the kernel warns you when a filesystem gets remounted read-only.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



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

2021-06-09 Thread Rick Thomas



On Wed, Jun 9, 2021, at 2:41 PM, John Paul Adrian Glaubitz wrote:
> Hello Rick!
> 
> On 6/9/21 11:34 PM, Rick Thomas wrote:
> > You're right that /boot/grub somehow has gotten read-only.  I didn't do that
> > myself, so something else must have done that.  Have you any clue you can 
> > share
> > with me as to which package I should re-file this report against?
> You are too quick in assuming that there might be a bug somewhere. We don't 
> know
> yet how and why the filesystem was re-mounted read-only. You should check your
> log files for any error messages or warnings.
> 
> Normally the kernel warns you when a filesystem gets remounted read-only.
> 
> Adrian

For what it's worth, the original install was not from February.  It was the 
April 17th iso images instead.

Searching "journalctl -b" I find:

> Jun 09 01:42:55 kmac kernel: hfs: filesystem was not cleanly unmounted, 
> running fsck.hfs is recommended.  mounting read-only.

I did have a brief power outage recently.  Maybe that's what caused the "not 
cleanly unmounted".

I'll try unmounting it and running fsck.hfs...
Hmmm... 
> root@kmac:~# fsck.hfs -f -C0 /boot/grub
> -bash: fsck.hfs: command not found

Am I missing a package somewhere?
Rick



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

2021-06-09 Thread John Paul Adrian Glaubitz
On 6/9/21 11:58 PM, Rick Thomas wrote:
>> Jun 09 01:42:55 kmac kernel: hfs: filesystem was not cleanly unmounted, 
>> running fsck.hfs is recommended.  mounting read-only.
> 
> I did have a brief power outage recently.  Maybe that's what caused the "not 
> cleanly unmounted".

If both machines were running when the power went away, you have your 
explanation here.

> I'll try unmounting it and running fsck.hfs...
> Hmmm... 
>> root@kmac:~# fsck.hfs -f -C0 /boot/grub
>> -bash: fsck.hfs: command not found
> 
> Am I missing a package somewhere?

Install "hfsprogs", it's in the "unreleased" distribution.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



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

2021-06-09 Thread Rick Thomas



On Wed, Jun 9, 2021, at 2:58 PM, Rick Thomas wrote:
> 
> 
> On Wed, Jun 9, 2021, at 2:41 PM, John Paul Adrian Glaubitz wrote:
> > Hello Rick!
> > 
> > On 6/9/21 11:34 PM, Rick Thomas wrote:
> > > You're right that /boot/grub somehow has gotten read-only.  I didn't do 
> > > that
> > > myself, so something else must have done that.  Have you any clue you can 
> > > share
> > > with me as to which package I should re-file this report against?
> > You are too quick in assuming that there might be a bug somewhere. We don't 
> > know
> > yet how and why the filesystem was re-mounted read-only. You should check 
> > your
> > log files for any error messages or warnings.
> > 
> > Normally the kernel warns you when a filesystem gets remounted read-only.
> > 
> > Adrian
> 
> For what it's worth, the original install was not from February.  It 
> was the April 17th iso images instead.
> 
> Searching "journalctl -b" I find:
> 
> > Jun 09 01:42:55 kmac kernel: hfs: filesystem was not cleanly unmounted, 
> > running fsck.hfs is recommended.  mounting read-only.
> 
> I did have a brief power outage recently.  Maybe that's what caused the 
> "not cleanly unmounted".
> 
> I'll try unmounting it and running fsck.hfs...
> Hmmm... 
> > root@kmac:~# fsck.hfs -f -C0 /boot/grub
> > -bash: fsck.hfs: command not found
> 
> Am I missing a package somewhere?
> Rick

Yep, I was missing hfsprogs.  I installed that and was able to do the fsck.hfs, 
then remounted /boot/grub and all was well.

So the only remaining question is "why was hfsprogs not automatically install 
on a G5 PowerMac?"

Thanks to all for your help in fixing this!

Rick
 



Re: OT: Huge Right to Repair Win for Consumers

2021-06-09 Thread Paul Wise
On Tue, Jun 8, 2021 at 11:54 PM Jeffrey Walton wrote:

> This is not as off-topic as it may seem. In the US, the FTC just
> issued a report that favors consumers.

A link to the report and related discussion:

https://www.ftc.gov/system/files/documents/reports/nixing-fix-ftc-report-congress-repair-restrictions/nixing_the_fix_report_final_5521_630pm-508_002.pdf
https://news.ycombinator.com/item?id=27068574

> The report and its recommendations may provide a means
> to pierce the veil of closed platforms, like closed-sourced firmware.

It seems unlikely to me that we will ever see a "Right to Repair" for
software, firmware or gateware.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

2021-06-09 Thread John Paul Adrian Glaubitz
On 6/10/21 12:14 AM, Rick Thomas wrote:
> So the only remaining question is "why was hfsprogs not automatically install 
> on a G5 PowerMac?"

See: https://lists.debian.org/debian-powerpc/2021/04/msg00129.html

and: https://lists.debian.org/debian-powerpc/2021/05/msg00012.html

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Re: OT: Huge Right to Repair Win for Consumers

2021-06-09 Thread John Paul Adrian Glaubitz
On 6/10/21 2:08 AM, Paul Wise wrote:
>> The report and its recommendations may provide a means
>> to pierce the veil of closed platforms, like closed-sourced firmware.
> 
> It seems unlikely to me that we will ever see a "Right to Repair" for
> software, firmware or gateware.

So, why should laws protect the intellectual property of software companies
but not the IP of hardware companies?

What supporters euphemistically call a "right to repair" is in reality an
initiative against the right of companies to protect their intellectual
property.

Why should any company take the risk of investment for new hardware developments
when they have to fear that every other company in the world will get free 
access
to their blue prints?

The claim that hardware companies intentionally make it hard to repair consumer
products is a conspiracy theory. In reality, a consumer product is primarily 
optimized
for production costs which implies cheap capacitors or cases that are glued 
together.

Lots of consumers seem to forget that a product sold into the market not only 
must
cover the material costs but also the costs of engineering, marketing, customer
support, customs, compliance tests and so on. And in the end, you still want 
there
to be a small profit left which is what makes the whole business model viable in
the first place.

If law initiatives also now want to take away the exclusive rights of hardware 
designers
over their blueprints and hence the market advantage over competitors that they 
took an
investment risk for, companies will lose the incentive to design and develop new
products.

Companies aren't charities so in the end they must protect their investments 
and have to
make profits to survive.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913