You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I experienced the reported bug on debian package tracker here which consist in a bad mount point for boot folder when trying to upgrade from bullseye to bookworm. In bullseye mount folder is /boot, trying to upgrade to bookworm, it fails at raspi-firmware package as it expect the boot folder in /boot/firmware instead of /boot. It would be nice to have working upgrade path.
I thought it was an issue in the debian package so I opened a PR in the debian gitlab instance here to fix this issue. But maintainer said it should be reported to raspbian folks. So here I am, hopefully in the right place.
The text was updated successfully, but these errors were encountered:
/boot/firmware is the right and expected mount point. This is a change from Bullseye, which is why we recommend starting with a clean install, rather than upgrading.
If something can be done, I recommend to fix this, I don't think it should be to difficult, you cannot ask users for reinstalling the system every time you need to upgrade... Part of the work is already done in the PR I point to
It works on our distro only, but you should be able to extract the required steps. When this has been tested sufficiently, I'll create one from it which runs on RPi OS.
Hi, I experienced the reported bug on debian package tracker here which consist in a bad mount point for boot folder when trying to upgrade from bullseye to bookworm. In bullseye mount folder is /boot, trying to upgrade to bookworm, it fails at raspi-firmware package as it expect the boot folder in /boot/firmware instead of /boot. It would be nice to have working upgrade path.
I thought it was an issue in the debian package so I opened a PR in the debian gitlab instance here to fix this issue. But maintainer said it should be reported to raspbian folks. So here I am, hopefully in the right place.
The text was updated successfully, but these errors were encountered: