That is normal. apt would prefer to drop privileges during the early stages when it is "downloading" packages and resolving dependencies. But presumably your home directory is not world-searchable (o+x), so it cannot be accessed by other unprivileged users. So apt falls back to running as root, which is not really a concern because it will need to run as root during the install stage anyway.Would I expect this at the end of the above install?
Notice: Download is performed unsandboxed as root as file '/home/pi/rpi-self-update_1.0-1_arm64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
I got a more serious error from apt:
Code:
The following packages have unmet dependencies: rpi-self-update:arm64 : Depends: busybox-static:arm64 but it is not installableE: Unable to correct problems, you have held broken packages.Looking at the source, I do not think I trust it to realise that bullseye has the FAT mounted on /boot, rather than /boot/firmware.
I am brave enough to attempt a conversion from bullseye32 to trixie64 remotely. I have done this kind of thing myself using tools such as debootstrap. I would not be brave enough to release scripts to do it. I am not sure who this project is for.
Statistics: Posted by jojopi — Fri Jun 19, 2026 11:13 pm







